Bit2Me Account Deprecated Methods API
The Account Deprecated Methods API from Bit2Me — 5 operation(s) for account deprecated methods.
Work with this as data
Every API here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for apis
7 MCP tools reach this
find_apisBrowse and filter every API in the catalog.get_api_artifactsOne API's artifacts, grouped by type.get_openapiThe primary OpenAPI for this API.find_similar_apisAPIs that look like this one.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This API
curl "https://apis.io/api/v1/apis/bit2me:bit2me-account-deprecated-methods-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.
OpenAPI Specification
openapi: 3.2.0
info:
title: Bit2Me API Gateway Account Deprecated Methods API
version: 2.0.0
tags:
- name: Account Deprecated Methods
paths:
/v1/account/employment-status:
get:
deprecated: true
description: '**This endpoint is deprecated.** Use `GET /v2/account/employment-status` instead, which
returns translation keys instead of pre-translated text.'
parameters:
- description: ISO 639-1 language code for translations (e.g. `es`, `en`).
in: query
name: langCode
required: true
schema:
pattern: ^[a-z]{2}$
type: string
responses:
'200':
content:
application/json:
schema:
properties:
data:
items:
properties:
description:
type: string
id:
type: string
langCode:
type: string
name:
type: string
type: object
type: array
total:
type: number
required:
- total
- data
type: object
description: List of employment status options.
'403':
content:
application/json:
example:
code: 403
description: invalid credentials
schema:
description: 'Returned with `403` when the request is rejected before being processed at all: the API key,
the signature or the nonce could not be validated. It is deliberately vague about which one
failed.
Note the status is `403` and not `401`, and that this envelope shares no field with any other
error shape in the API.
'
properties:
code:
description: Repeats the HTTP status code.
enum:
- 403
example: 403
type: integer
description:
description: Fixed message; it never carries detail about the specific failure.
example: invalid credentials
type: string
required:
- code
- description
type: object
description: Invalid credentials.
default:
content:
application/json:
schema:
properties:
data:
type: object
error:
type: string
message:
type: string
reqId:
type: string
statusCode:
type: number
required:
- message
- error
type: object
description: Unexpected error.
security:
- JwtAuth: []
- ApiKeyAuth: []
summary: Deprecated, use GET /v2/account/employment-status instead
tags:
- Account Deprecated Methods
x-product:
wallet: Account
x-use: GET /v2/account/employment-status
operationId: getV1AccountEmploymentStatus
x-operation-id-source: derived
/v1/account/funds-origin:
get:
deprecated: true
description: '**This endpoint is deprecated.** Use `GET /v2/account/funds-origin` instead, which returns
translation keys instead of pre-translated text.'
parameters:
- description: ISO 639-1 language code for translations (e.g. `es`, `en`).
in: query
name: langCode
schema:
pattern: ^[a-z]{2}$
type: string
responses:
'200':
content:
application/json:
schema:
properties:
data:
items:
properties:
description:
type: string
id:
type: string
langCode:
type: string
name:
type: string
type: object
type: array
total:
type: number
required:
- total
- data
type: object
description: List of fund origin options.
'403':
content:
application/json:
example:
code: 403
description: invalid credentials
schema:
description: 'Returned with `403` when the request is rejected before being processed at all: the API key,
the signature or the nonce could not be validated. It is deliberately vague about which one
failed.
Note the status is `403` and not `401`, and that this envelope shares no field with any other
error shape in the API.
'
properties:
code:
description: Repeats the HTTP status code.
enum:
- 403
example: 403
type: integer
description:
description: Fixed message; it never carries detail about the specific failure.
example: invalid credentials
type: string
required:
- code
- description
type: object
description: Invalid credentials.
default:
content:
application/json:
schema:
properties:
data:
type: object
error:
type: string
message:
type: string
reqId:
type: string
statusCode:
type: number
required:
- message
- error
type: object
description: Unexpected error.
security:
- JwtAuth: []
- ApiKeyAuth: []
summary: Deprecated, use GET /v2/account/funds-origin instead
tags:
- Account Deprecated Methods
x-product:
wallet: Account
x-use: GET /v2/account/funds-origin
operationId: getV1AccountFundsOrigin
x-operation-id-source: derived
/v1/account/professions:
get:
deprecated: true
description: '**This endpoint is deprecated.** Use `GET /v2/account/professions` instead, which returns
translation keys instead of pre-translated text.'
parameters:
- description: ISO 639-1 language code for translations (e.g. `es`, `en`).
in: query
name: langCode
schema:
pattern: ^[a-z]{2}$
type: string
responses:
'200':
content:
application/json:
schema:
properties:
data:
items:
properties:
description:
type: string
id:
type: string
langCode:
type: string
professionCode:
type: string
required:
- id
- description
- professionCode
- langCode
type: object
type: array
total:
type: integer
required:
- total
- data
type: object
description: List of professions.
'403':
content:
application/json:
example:
code: 403
description: invalid credentials
schema:
description: 'Returned with `403` when the request is rejected before being processed at all: the API key,
the signature or the nonce could not be validated. It is deliberately vague about which one
failed.
Note the status is `403` and not `401`, and that this envelope shares no field with any other
error shape in the API.
'
properties:
code:
description: Repeats the HTTP status code.
enum:
- 403
example: 403
type: integer
description:
description: Fixed message; it never carries detail about the specific failure.
example: invalid credentials
type: string
required:
- code
- description
type: object
description: Invalid credentials.
default:
content:
application/json:
schema:
properties:
data:
type: object
error:
type: string
message:
type: string
reqId:
type: string
statusCode:
type: number
required:
- message
- error
type: object
description: Unexpected error.
security:
- JwtAuth: []
- ApiKeyAuth: []
summary: Deprecated, use GET /v2/account/professions instead
tags:
- Account Deprecated Methods
x-product:
wallet: Account
x-use: GET /v2/account/professions
operationId: getV1AccountProfessions
x-operation-id-source: derived
/v1/account/purposes:
get:
deprecated: true
description: '**This endpoint is deprecated.** Use `GET /v2/account/purposes` instead, which returns
translation keys instead of pre-translated text.'
parameters:
- description: ISO 639-1 language code for translations (e.g. `es`, `en`).
in: query
name: langCode
schema:
pattern: ^[a-z]{2}$
type: string
responses:
'200':
content:
application/json:
schema:
properties:
data:
items:
properties:
description:
type: string
id:
type: string
langCode:
type: string
name:
type: string
required:
- id
- name
- description
- langCode
type: object
type: array
total:
type: integer
required:
- total
- data
type: object
description: List of account purposes.
'403':
content:
application/json:
example:
code: 403
description: invalid credentials
schema:
description: 'Returned with `403` when the request is rejected before being processed at all: the API key,
the signature or the nonce could not be validated. It is deliberately vague about which one
failed.
Note the status is `403` and not `401`, and that this envelope shares no field with any other
error shape in the API.
'
properties:
code:
description: Repeats the HTTP status code.
enum:
- 403
example: 403
type: integer
description:
description: Fixed message; it never carries detail about the specific failure.
example: invalid credentials
type: string
required:
- code
- description
type: object
description: Invalid credentials.
default:
content:
application/json:
schema:
properties:
data:
type: object
error:
type: string
message:
type: string
reqId:
type: string
statusCode:
type: number
required:
- message
- error
type: object
description: Unexpected error.
security:
- JwtAuth: []
- ApiKeyAuth: []
summary: Deprecated, use GET /v2/account/purposes instead
tags:
- Account Deprecated Methods
x-product:
wallet: Account
x-use: GET /v2/account/purposes
operationId: getV1AccountPurposes
x-operation-id-source: derived
/v2/account/address:
get:
deprecated: true
description: '**This endpoint is deprecated.** Use `GET /v3/account/address` instead, which returns
addresses with sensitive data masked except for the country code.'
parameters:
- description: Filter by a specific address UUID. When omitted, all addresses are returned.
in: query
name: addressId
schema:
format: uuid
type: string
- description: Filter by residence flag.
in: query
name: isResidence
schema:
type: boolean
responses:
'200':
content:
application/json:
example:
- city: Madrid
countryCode: ES
id: 550e8400-e29b-41d4-a716-446655440000
isDefaultAddress: true
isResidence: true
stateCode: MD
streetAddress: Calle Ejemplo 1
zip: '28001'
schema:
items:
properties:
alias:
maxLength: 50
type: string
city:
type: string
countryCode:
pattern: ^[A-Z]{2}$
type: string
id:
type: string
isDefaultAddress:
type: boolean
isResidence:
type: boolean
stateCode:
type: string
streetAddress:
type: string
userId:
type: string
zip:
type: string
required:
- streetAddress
- city
- stateCode
- zip
- countryCode
type: object
type: array
description: User addresses.
'403':
content:
application/json:
example:
code: 403
description: invalid credentials
schema:
description: 'Returned with `403` when the request is rejected before being processed at all: the API key,
the signature or the nonce could not be validated. It is deliberately vague about which one
failed.
Note the status is `403` and not `401`, and that this envelope shares no field with any other
error shape in the API.
'
properties:
code:
description: Repeats the HTTP status code.
enum:
- 403
example: 403
type: integer
description:
description: Fixed message; it never carries detail about the specific failure.
example: invalid credentials
type: string
required:
- code
- description
type: object
description: Invalid credentials.
'404':
content:
application/json:
schema:
properties:
data:
type: object
error:
type: string
message:
type: string
reqId:
type: string
statusCode:
type: number
required:
- message
- error
type: object
description: User not found.
default:
content:
application/json:
schema:
properties:
data:
type: object
error:
type: string
message:
type: string
reqId:
type: string
statusCode:
type: number
required:
- message
- error
type: object
description: Unexpected error.
security:
- JwtAuth: []
- ApiKeyAuth: []
summary: Deprecated, use GET /v3/account/address instead
tags:
- Account Deprecated Methods
x-product:
wallet: Account
x-use: GET /v3/account/address
operationId: getV2AccountAddress
x-operation-id-source: derived
components:
securitySchemes:
ApiKeyAuth:
description: 'For accessing these endpoints a valid API key must be sent in the *X-Api-Key* header.
'
in: header
name: X-Api-Key
type: apiKey
BasicAuth:
description: "Access control to the API is always controlled by a JWT token. To get this token you must log in through */v3/signin* (email and password).\n\nThe client sends requests with the Authorization header that contains the Basic word followed by a space and a base64-encoded username:password string.\nExample:\n Authorization: Basic ZGVtbzpwQDU1dzByZA==\n"
in: header
name: Authorization
type: apiKey
CustomApiKey:
description: 'For accessing a specific API endpoint of this type, a valid API key must be passed in the *Authorization* header.
'
in: header
name: Authorization
type: apiKey
JwtAuth:
description: "For accessing the API a valid JWT token must be passed in the *Authorization* header.\n\nA valid JWT token is generated by the API and returned after calling */v1/signin* with valid credentials.\n\nExample:\n Authorization: Bearer xxxxxx.yyyyyyy.zzzzzz\n"
in: header
name: Authorization
type: apiKey
JwtPreAuth:
description: "The pre-auth token proves the password only, while a sign-in waits for its second step. It is the\n*accessToken* returned with *sfa: true* by *POST /v4/signin* or *POST /v2/signin/oauth/{provider}*.\nSend it in the *Authorization* header as a Bearer token.\n\nIt is accepted only by these routes:\n - *POST /v1/auth/two-step-verification/initiate*\n - *POST /v1/auth/two-step-verification/reissue*\n - *POST /v1/auth/two-step-verification/verify*\n - *POST /v4/signin/sfa*\n\nsuite-auth verifies the token on every call (it is never cached). A refused token is answered with 403.\n\nExample:\n Authorization: Bearer xxxxxx.yyyyyyy.zzzzzz\n"
in: header
name: Authorization
type: apiKey
x-tagGroups:
- name: Basic Info
tags:
- Crypto Suite
- name: Crypto Suite Endpoints
tags:
- Account
- Accounting
- Affiliates
- Auth
- Blockchain Manager
- Brokerage
- Captcha
- Card
- Card Authorizator
- Card Loyalty
- Collection Orders
- Commerce
- Compliance
- Configuration
- Crypto Credentials
- Currency
- Currency Analytics
- Currency Collections
- Currency Favorites
- Earn
- External Onboarding
- Instant
- Junior
- Launchpad
- Loan
- Misc
- Notification
- Portfolio
- Portfolio Analytics
- Price Alert Scheduler
- Price Orders
- Price Watchdog
- Promotion
- Recurring Orders
- Pay
- Redeem Token
- Space Center
- Stocks
- Support
- Taxes
- Teller
- Terms and Conditions
- Travel Rule
- Trading
- Translations
- UX
- Verifier
- Wallet
- name: Deprecated
tags:
- Account Deprecated Methods
- Auth Deprecated Methods
- Currency Deprecated Methods
- Earn Deprecated Methods
- Verifier Deprecated Methods