transactionsCreate a manual transaction

Create a manual transaction

Creates a manual transaction. Requires the transactions:write scope, writes_enabled, and an Idempotency-Key (a double-fired create would otherwise post the same spending twice).

The target account must be visible to this connection: an excluded account and a nonexistent one both return 404, byte-identical, so a hidden account cannot be found by probing which ids accept a write. The same holds for category_id.

Returns 200, not 201. Every write on this API serves 200 so that a replayed response is byte-identical to the original — a replay cannot honestly claim to have created anything, and two different status codes for one stored response would be worse than the REST purism is worth.

curl -X POST "https://api.403fin.io/v1/transactions" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: example_string" \
  -H "Authorization: Bearer YOUR_API_TOKEN" \
  -H "X-API-Key: YOUR_API_KEY" \
  -d '{
  "account_id": "123e4567-e89b-12d3-a456-426614174000",
  "amount": "example_string",
  "currency_code": "example_string",
  "merchant": "example_string",
  "description": "example_string",
  "date": "2024-12-25",
  "category_id": "123e4567-e89b-12d3-a456-426614174000",
  "tags": [
    "example_string"
  ],
  "memo": "example_string",
  "location": {
    "street": "example_string",
    "city": "New York",
    "state": "example_string",
    "postal_code": "example_string",
    "country": "USA"
  }
}'
{
  "data": {
    "id": "123e4567-e89b-12d3-a456-426614174000",
    "account_id": "123e4567-e89b-12d3-a456-426614174000",
    "category_id": "123e4567-e89b-12d3-a456-426614174000",
    "amount": {
      "amount": "example_string",
      "currency": "example_string"
    },
    "merchant": "example_string",
    "display_name": "John Doe",
    "description": "example_string",
    "date": "2024-12-25",
    "posted_at": "2024-12-25T10:00:00Z",
    "is_pending": true,
    "source": "example_string",
    "payment_channel": "example_string",
    "transfer_pair_id": "123e4567-e89b-12d3-a456-426614174000",
    "recurring_rule_id": "123e4567-e89b-12d3-a456-426614174000",
    "external_ref": "example_string",
    "tags": [
      "example_string"
    ],
    "check_number": "example_string",
    "memo": "example_string",
    "location": {
      "street": "example_string",
      "city": "New York",
      "state": "example_string",
      "postal_code": "example_string",
      "country": "USA"
    },
    "provider_amount": {
      "amount": "example_string",
      "currency": "example_string"
    },
    "provider_merchant_name": "John Doe",
    "provider_transaction_date": "2024-12-25",
    "provider_description": "example_string",
    "provider_memo": "example_string",
    "version": 42,
    "created_at": "2024-12-25T10:00:00Z",
    "updated_at": "2024-12-25T10:00:00Z"
  },
  "pagination": {
    "next_cursor": "example_string",
    "has_more": true
  },
  "redacted_fields": [
    "example_string"
  ],
  "filtered": true
}
POST
/v1/transactions
POST
Base URLstring

Target server for requests. Edit to use your own host.

Bearer Token
Bearer Tokenstring
Required

An opaque ff_ credential (ff_ak_ / ff_at_) presented as a Bearer token.

An opaque ff_ credential (ff_ak_ / ff_at_) presented as a Bearer token.
API Key (header: X-API-Key)
X-API-Keystring
Required

An opaque ff_ credential presented in the X-API-Key header.

An opaque ff_ credential presented in the X-API-Key header.
Content-Typestring
Required

The media type of the request body

Options: application/json
header
Idempotency-Keystring
Required

A caller-chosen unique key (1-128 chars) that makes the write idempotent. A retry with the SAME key against the SAME operation, resource, and body replays the original response (Idempotency-Replayed: true). The same key with anything different — a changed body, a different endpoint, or a different {id} — is a 409 conflict; a still-in-flight duplicate is 409 with Retry-After. Required on every write. Stored for 24 hours. The key is bound to the target, not only to the payload, so reusing one key across two deletes (which carry no body at all) conflicts rather than replaying the first delete's response.

Min length: 1 • Max length: 128
amountstring
Required

A decimal amount string, negative for spending. Never a float.

currency_codestring

ISO 4217 code. Defaults to the account's currency.

datestring
Required

YYYY-MM-DD.

Format: date
category_idstring
Format: uuid
locationobject

A purchase location. Redacted as a single unit (transaction.location) — a city plus a postal code answers "where were you" as surely as a street line does, so the components are never hidden separately. On a write it is GROUP-REPLACE: the components sent become the whole stored location and omitted ones are cleared. Use clear_location to remove it entirely.

Request Preview
Response

Response will appear here after sending the request

Authentication

header
Authorizationstring
Required

Bearer token. An opaque ff_ credential (ff_ak_ / ff_at_) presented as a Bearer token.

header
X-API-Keystring
Required

API Key for authentication. An opaque ff_ credential presented in the X-API-Key header.

Headers

Idempotency-Keystring
Required

A caller-chosen unique key (1-128 chars) that makes the write idempotent. A retry with the SAME key against the SAME operation, resource, and body replays the original response (Idempotency-Replayed: true). The same key with anything different — a changed body, a different endpoint, or a different {id} — is a 409 conflict; a still-in-flight duplicate is 409 with Retry-After. Required on every write. Stored for 24 hours.

The key is bound to the target, not only to the payload, so reusing one key across two deletes (which carry no body at all) conflicts rather than replaying the first delete's response.

Body

application/json
amountstring
Required

A decimal amount string, negative for spending. Never a float.

currency_codestring

ISO 4217 code. Defaults to the account's currency.

locationobject

A purchase location. Redacted as a single unit (transaction.location) — a city plus a postal code answers "where were you" as surely as a street line does, so the components are never hidden separately. On a write it is GROUP-REPLACE: the components sent become the whole stored location and omitted ones are cleared. Use clear_location to remove it entirely.

Responses

dataobject
Required
paginationstring

Cursor pagination state, present on list endpoints.

redacted_fieldsstring[]

Field ids stripped from the payload by connection scope.

filteredboolean

True when row or aggregate filtering is in effect for this response.