Skip to Content

Issuing and its activation

GET
/v1/ec/businesses/{id}/issuing

Where a live business's issuing stands and what must be met before it is activated in live, with what to do in each case: a valid certificate, an emission point in live with its addresses, and an invoice authorized in test. It keeps its received documents in live whatever this says; only issuing waits for the activation, which a person makes from the console, and business.issuing_updated tells when the state or the lock moves. A sandbox business always issues: it answers active, ready with no checks.

Authorization

headerAuthorizationBearer <token>

Your API key, which acts for the one business it was created for: fb_live_… keys work at api.fiscalbase.io and issue in live, and fb_sandbox_… keys work at api-sandbox.fiscalbase.io and issue in sandbox, on the simulated SRI. A key sent to the other host is refused with api_key_wrong_host, which names its host.

Path Parameters

id*string
Formatuuid

Header Parameters

Fiscalbase-Environment?string

The environment the call acts in. Required with a person's session; a key's own environment is the one that counts, so a key may leave it out, and naming another is 422 environment_mismatch.

Value in"sandbox""test""live"
Fiscalbase-Business?string

The business the call acts for. With a person's session, the one the call is about (without it, a call about one business is 422 business_required and a list covers every business of the organization); a key acts for its own, so naming another is 422 business_mismatch.

Formatuuid
Fiscalbase-Channel?string

Which of Fiscalbase's own integrations a key's call comes from, recorded as the channel of the documents it issues: a record, not a permission. Without it, api. A person's call is always console.

Value in"api""mcp"
Fiscalbase-Agent?string

The AI agent a key's call comes from, as its client names itself (the MCP server sets it); recorded with the request and shown in the console's request log.

Response Body

The issuing state and its checklist

application/json
  1. response
allowed*boolean

Whether the business can issue in test and live now. sandbox businesses always can: they are free.

lock*|

What locks the business; null when nothing does. A lock pauses issuing in test and live. Reading and downloading every document, and the configuration (certificate, numbering, details), stay open under any lock.

state*string

off: it doesn't issue through Fiscalbase (its received documents are kept in live all the same); testing: it is rehearsing in test, with active numbering or a document of its own there; active: it issues in live since active_since. A sandbox business is always active, on the simulator.

Value in"off""testing""active"
active_since*|

When a person activated issuing in live; null until then, and always null on a sandbox business.

Formatdate-time
object*"issuing"
Value in"issuing"
business_id*string
Formatuuid
ready*boolean

Whether every check passes, so issuing can be activated.

checks*array<>
Example Request
curl -X GET 'https://api.fiscalbase.io/v1/ec/businesses/497f6eca-6276-4993-bfeb-53cbbbba6f08/issuing'
Example Response
{
  "object": "issuing",
  "business_id": "0199d0a4-1a2b-7c3d-8e4f-5a6b7c8d9e0f",
  "state": "testing",
  "active_since": null,
  "allowed": true,
  "lock": null,
  "ready": false,
  "checks": [
    {
      "code": "certificate",
      "passed": true,
      "message": "You have a valid signing certificate."
    },
    {
      "code": "issuing_point",
      "passed": false,
      "message": "Open numbering in 'live' at an establishment of your RUC, with the head office address and the establishment's."
    }
  ]
}