Create a new payments Vendor
Creates an accounting vendor that payments can be sent to.
There is no upsert. Ottimate matches the request against existing vendors in the company on name, ZIP code and street address, and returns 400 naming the existing vendor when it treats one as a duplicate. The response body of a successful create carries only the new vendor’s id; read the full record back with GET /v1/payments/vendor/{id}.
Send an Idempotency-Key header so a retried create cannot produce a second vendor.
Authentication
Headers
API version to use (optional, defaults to latest). Supported values: 1.0.0, 1.1.0.
Client-generated unique key (UUID/ULID recommended). JSON requests: the first 2xx response is cached for 24h and replayed on a same-key retry with a matching body; a different body returns 422. Non-JSON requests (e.g. file uploads): the key is single-use — any same-key retry returns 422 regardless of body. See Idempotency for full details.
Request
The Ottimate company ID to create this vendor in, as a numeric string (digits only). Your API user must have access to the company, or the request returns 401.
The two-letter state code of the vendor’s mailing address.
The two-letter ISO country code of the vendor’s mailing address.
The care-of name for the vendor’s mailing address.
Arbitrary key-value metadata to store on the vendor. Returned unchanged by GET /v1/payments/vendor/{id}.

