/api_curl/cashout_api/* → version retirement
Deprecated, no date
Payouts v2 has been deprecated without a shutdown date and is no longer recommended for new integrations. The change affects calls to /api_curl/cashout_api/* endpoints, which will eventually fail.
Calls it hits
/api_curl/cashout_api/*
What to use instead of these calls
Submit payouts with POST /payouts/v3 (Payouts v3), signing each request in the Payload-Signature header. Moving to Payouts v3 requires more than updating an endpoint, as it goes through your dLocal Technical Account Manager and requires implementing new request signing.
Moving to Payouts v3 goes through dLocal (the account's Technical Account Manager) and a new request signing.
In dLocal API's words
Payouts v2 is now deprecated and no longer recommended for new integrations.
Facts
- API
- dLocal API
api.dlocal.com - Kind
- Version retirement
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against dLocal API's own pages
Questions
When does this change take effect?
dLocal API deprecated /api_curl/cashout_api/* without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: dLocal API has not given a shutdown date yet.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix.