Skip to Content

Change an emission point and its establishment

PATCH
/v1/ec/establishments/{code}/emission-points/{point}

One administrative act, in one transaction: point changes the emission point's name or code on all its series in your key's environment (another system's punto takes a name too, like the system that issues there), and establishment changes its establishment's name, address or code on every series the establishment has. Each part says only what changed, and at least one is given. A code changes only while nothing was numbered under it (409 emission_point_already_numbered, 409 establishment_already_numbered); outside sandbox a new establishment code must be listed as open in the SRI registry, whose address it takes unless one is given. Either refusal leaves both as they were. series.updated says what changed on each series.

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

code*string
Match^\d{3}$
point*string
Match^\d{3}$

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.

Request Body

application/json
  1. body
point?
establishment?

Response Body

The series it changed

application/json
  1. response
object*"series_update"
Value in"series_update"
data*array<>

Each series of the establishment or point, already changed.

Example Request
curl -X PATCH 'https://api.fiscalbase.io/v1/ec/establishments/string/emission-points/string' \
  -H 'Content-Type: application/json' \
  -d '{}'
Example Response
{
  "object": "series_update",
  "data": [
    {
      "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08",
      "object": "series",
      "business_id": "f59fcbb7-848d-4242-af07-a8bb7e3ab37c",
      "environment": "sandbox",
      "type": "invoice",
      "establishment": "string",
      "emission_point": "string",
      "establishment_address": "string",
      "establishment_name": "string",
      "emission_point_name": "string",
      "issued_by": "fiscalbase",
      "active": true,
      "next_number": 1,
      "last_number_seen": 0,
      "last_seen_on": "2019-08-24",
      "seen_this_month": 0,
      "issued_today": 0,
      "gaps": {
        "count": 0,
        "oldest_missing": 0
      },
      "created_at": "2019-08-24T14:15:22Z",
      "updated_at": "2019-08-24T14:15:22Z"
    }
  ]
}