In this article, you will find a curated, chronologically ordered list of notable changes to the Dataddo Headless API.
2024-06
Updates to authorization process
Update
Required Action
/revoke endpoint introduced for invalidating the access token
No action is required.
realm_id and provider params no longer needed
Please remove the references to these parameters from your codebase.
App Flow method added for working with OAuth 2.0 services
Update
Required Action
App Flow method added, further simplifiend the authorization process of OAuth 2.0 services.
No action is required.
Changing parameter names for authorization endpoints
Update
Required Action
Parameter service changed to serviceName.
Change parameter name in your codebase. It will be fully removed in Q4 2024
Parameter data changed to config.
Change parameter name in your codebase. It will be fully removed in Q4 2024
2024-05 Updates
SocialBakers Updated to Emplifi
Update
Required Action
SocialBakers connector has been updated to Emplifi.
Please update all SocialBakers references to Emplifi.
2024-02 Updates
Deprecation of the storage Field
Update
Required Action
The storage field will be deprecated on February 28, 2024.
Please update to the new storageStrategy field as soon as possible.
Deprecation of the email Field from /action/authorization
Update
Required Action
The email field will be deprecated on June 30, 2024.
Please start using label field instead.
Simplified Response Format for Request Data Validation Errors
Update
Required Action
The response format for request data validation errors (API requests with missing required parameters) was updated to be clearer and more intuitive.
No action is required on your part.
// old
{
"correlation_id": "89f7f3b5bbab34a015d032831b217923",
"code": "REQUEST_VALIDATION_ERROR",
"message": "Request validator error [password]: This value should be of type int.",
"detail": [
{
"password": "This value should be of type int.",
},
{
"password": "This value is not a valid country.",
},
{
"email": "This value should be of type int."
}
]
}
// new
{
"correlation_id": "89f7f3b5bbab34a015d032831b217923",
"code": "REQUEST_VALIDATION_ERROR",
"message": "Request validator error [password]: This value should be of type int.",
"detail": {
"password": [
"This value should be of type int.",
"This value is not a valid country."
],
"email": [
"This value should be of type int."
]
}
}
2023-11 Updates
Deprecation of API Endpoints
Update
Required action
As of November 1, 2023, the following API endpoints will be deprecated.
Please migrate to the new API endpoints before November 1, 2023.
POST /sources/{id}/extraction/run
POST /sources/{id}/extraction/enqueue
POST /flows/{id}/write/run
POST /flows/{id}/write/enqueue
GET /flows/{id}/write/run
GET /sources/{id}/status
GET /flows/{id}/status
These endpoints are used for the current status of an action, whether the action has been completed or not:
GET /sources/{id}/status
GET /flows/{id}/status
Was this article helpful?
Thank you for your feedback! Our team will get back to you
