Live / Incidents / Bit2Me
Bit2Me: API Update: Endpoint Deprecation
Bit2Me · bit2me.comImpact: nonemonitoring2026-07-09 14:20 UTC
Public — what happened
Summary
Duration: 6 months
Bit2Me will be deprecating the following endpoints on January 11, 2027. This change will affect users currently using the deprecated endpoints.
POST /v1/account/address
GET /v2/account/address
POST /v1/account/reset/password
PUT /v1/account/reset/password
PUT /v1/account/verify/phone
GET /v1/account/professions
GET /v1/account/purposes
GET /v1/account/employment-status
GET /v1/account/funds-origin
GET /v1/account/politically-exposed
GET /v1/account/identity-type/all
PUT /v2/account/reset/password
POST /v2/account/sfa/call
GET /v1/card/cards/{cardId}/balance
PATCH /v1/card/cards/{cardId}/activate
POST /v1/card/payments/proforma
POST /v1/card/payments/{paymentId}/proforma
Timeline
- Started — 2026-07-09 14:20 UTC
- Last update — 2026-07-09 14:20 UTC
- Ongoing at last check.
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Bit2Me against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Bit2Me: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Bit2Me report →