Vision Developers
POST/apps/accounting/v1/invoices/{reference}/pay-link

Make (or return, or with rotate replace) the pay link of an issued invoice.

The approved contract does not provide a longer purpose statement for this operation.

App
Accounting
Contract
Accounting API 0.32.0
Lifecycle
preview
Runtime
not-public
Operation ID
createInvoicePayLink
Canonical origin
https://accounting.runonvision.com

Availability: This is a preview contract with runtime status not-public. Publication documents an approved interface; it does not imply public production access.

Purpose and use cases

Make (or return, or with rotate replace) the pay link of an issued invoice.

The owning App is Vision Accounting. Accounting owns financial records, exact arithmetic, approvals, audit evidence, workspace grants, and ledger invariants.

Business use cases and out-of-scope behavior are not yet declared in the approved OpenAPI description.

Request

POST https://accounting.runonvision.com/apps/accounting/v1/invoices/{reference}/pay-link

Authentication and authorization

Send a Vision-issued bearer token for the exact App audience. The token must include the accounting entitlement and satisfy the aws-… accounting workspace required binding.

  • Required scope: accounting:invoices:issue

Human roles are not declared in OpenAPI. Record-level and business permission checks remain the owning App's authority.

Headers

  • Authorization: Bearer <access-token> — required.
  • Accept: application/json — recommended where a JSON response is declared.
  • Content-Type: application/json — required for the documented request representation.

Undeclared tracing, idempotency, conditional-request, and version headers are not assumed on this page.

Path and query parameters

NameLocationTypeRulesDescription
referencepathstringrequired; pattern ^INV-[A-Z0-9]{12}$Not described in the contract.
Idempotency-Keyheaderstringrequired; minimum length 16; maximum length 160; pattern ^[A-Za-z0-9._:-]+$Not described in the contract.

Request body

Media type: application/json. The body is required.

FieldTypeRulesDescription
schemaVersion"vision-accounting-invoice-pay-link.v1"requiredNot described in the contract.
rotatebooleanoptional; default falseReplace the current link. The old link stops working at once.

Runnable examples

Placeholder values are generated from the approved schema and are not live credentials or customer data. Replace every angle-bracket or shell variable value. Examples cannot be run until the App has a routed base URL and your client has the required grant.

cURL
curl 'https://accounting.runonvision.com/apps/accounting/v1/invoices/${REFERENCE}/pay-link' \
  --request POST \
  --header 'authorization: Bearer ${ACCESS_TOKEN}' \
  --header 'accept: application/json' \
  --header 'content-type: application/json' \
  --data '{
    "schemaVersion": "vision-accounting-invoice-pay-link.v1",
    "rotate": false
  }'
JavaScript (server-side)
const response = await fetch('https://accounting.runonvision.com/apps/accounting/v1/invoices/${REFERENCE}/pay-link', {
  method: 'POST',
  headers: {
    authorization: `Bearer ${ACCESS_TOKEN}`,
    accept: 'application/json',
    'content-type': 'application/json',
  },
  body: JSON.stringify({
  "schemaVersion": "vision-accounting-invoice-pay-link.v1",
  "rotate": false
}),
}

if (!response.ok) throw new Error(`Vision API ${response.status}`)
const result = await response.json()
Python 3 standard library
import json
import urllib.parse
import urllib.request

request = urllib.request.Request(
    'https://accounting.runonvision.com/apps/accounting/v1/invoices/${REFERENCE}/pay-link',
    data=json.dumps({"schemaVersion":"vision-accounting-invoice-pay-link.v1","rotate":false}).encode(),
    headers={
    "Accept": "application/json",
    "Authorization": "Bearer <ACCESS_TOKEN>",
    "Content-Type": "application/json"
},
    method='POST',
)
with urllib.request.urlopen(request, timeout=30) as response:
    result = json.load(response)

The current TypeScript reference client covers Platform token exchange and core reads. No native SDK helper is declared for this operation; use the HTTP contract directly and follow the SDK guidance.

Responses

StatusMeaningSchema
200Pay linkobject
400Safe Accounting errorobject
401Safe Accounting errorobject
403Safe Accounting errorobject
404Safe Accounting errorobject
409Safe Accounting errorobject
503Safe Accounting errorobject

Success response schema

FieldTypeRulesDescription
schemaVersion"vision-accounting-invoice-pay-link.v1"requiredNot described in the contract.
subjectReferencestringoptional; pattern ^INV-[A-Z0-9]{12}$Not described in the contract.
payUrlstring | null · urirequiredNot described in the contract.
linkVersioninteger | nullrequiredNot described in the contract.
200 illustrative response
{
  "schemaVersion": "vision-accounting-invoice-pay-link.v1",
  "subjectReference": "<subjectReference>",
  "payUrl": "<payUrl>",
  "linkVersion": "<linkVersion>"
}

Errors and troubleshooting

Error bodies and codes are shown only where the approved contract declares them. Use status, the declared error schema, and any correlation identifier returned by the App; do not infer that two Apps share one envelope.

  • 400 — Safe Accounting error
  • 401 — Safe Accounting error
  • 403 — Safe Accounting error
  • 404 — Safe Accounting error
  • 409 — Safe Accounting error
  • 503 — Safe Accounting error

Collection behavior

Pagination: not declared. Filtering/search: not declared. Sorting: not declared.

Cursor lifetime, cursor binding, stable ordering, maximum traversal, and unknown-filter behavior are not assumed unless stated by a parameter description or schema constraint above.

Operational behavior

  • Rate limit: No operation-specific limit or 429 response is declared.
  • Retry: Retry only when the documented error model or response headers authorize it. Timeout and backoff values are not declared by this operation.
  • Idempotency: No idempotency header or replay window is declared.
  • Concurrency: No ETag, If-Match, or optimistic-version header is declared.

Security and privacy

  • Keep client credentials and bearer tokens on trusted servers.
  • Send only to the exact approved HTTPS origin and audience.
  • Treat response data according to the owning App's classification and retention policy; the OpenAPI contract does not itself grant data access.
  • Do not log credentials, tokens, complete private payloads, or secrets.

Edge cases and known documentation gaps

  • No detailed operation description.
  • One or more parameters have no field-level description.
  • The request body has no purpose or conditional-rule description.
  • Business roles, timeout, retry budget, rate value, idempotency window, and concurrency behavior are absent unless explicitly stated above.

Contract history and evidence