Square API
/v2/customers/{id}/cards* endpoint removal
Deprecated, no dateSubscribe to Square APIShare
Square has deprecated the /v2/customers/{id}/cards* endpoints without a shutdown date. The deprecation applies to the CreateCustomerCard endpoint, the DeleteCustomerCard endpoint, and the Customer.cards field. Once removed, requests to these endpoints will fail.
Calls it hits
/v2/customers/{id}/cards*
What to use instead of these calls
Save cards using the Cards API by calling POST /v2/cards with the customer_id, and disable them with POST /v2/cards/{card_id}/disable. Handle gift cards separately with the Gift Cards API.
In Square API's words
The CreateCustomerCard endpoint, DeleteCustomerCard endpoint, and Customer.cards field are deprecated.
Facts
- API
- Square API
connect.squareup.com - Kind
- Endpoint removal
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Square API's own pages
Questions
When does this change take effect?
Square API deprecated /v2/customers/{id}/cards* without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Square 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.
More from Square API 5
-
POST /v2/paymentsParameter removal Stopped working -
POST /mobile/authorization-codeEndpoint removal Stopped working -
POST /v2/locations/{id}/transactions*Endpoint removal Stopped working -
No date
/v2/labor/shifts*Endpoint removal Deprecated, no date -
No date
GET /v2/locations/{id}/transactions*Endpoint removal Deprecated, no date
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix.