---
title: "Check whether a portfolio NIF can issue"
method: GET
path: "/accounts/{account}/companies/{company}/issuing-readiness"
tags: ["Companies"]
---

# Check whether a portfolio NIF can issue

`GET /accounts/{account}/companies/{company}/issuing-readiness`

## Request

- Base URL: `https://api.factuarea.com/v1`
- URL: `https://api.factuarea.com/v1/accounts/{account}/companies/{company}/issuing-readiness`
- Auth: one of:
  - HTTP bearer
  - API key in header `X-API-Key`

Check whether a NIF within your credential scope is ready to issue invoices: `can_issue`, a closed list of `blockers` and the composing signals.
- Neutral read: it never reports plan, quota or price, and never returns a payment-required state.
- Unknown, foreign or out-of-scope NIFs all return the same 404 `resource_not_found` (`param: company`).

## Path parameters

- `account` string, uuid, required
- `company` string, uuid, required

## Headers

- `Factuarea-Version` string, date

## Response `200`

- object
  - `data` IssuingReadiness, required: Whether a NIF can issue documents right now, and what stands in the way when it cannot. `can_issue` is the verdict and `blockers` the reasons: an empty `blockers` with `can_issue` false would be a bug, because a refusal that cannot be named cannot be fixed.
    - `can_issue` boolean, required: The verdict. `true` only when every condition below is met.
    - `blockers` string[], required: Machine-readable reasons the NIF cannot issue, in no particular order. Empty when `can_issue` is `true`. `verifactu_certificate_missing` means VeriFactu is enabled for the NIF but it has no valid certificate (none, revoked or expired). New reasons may be added over time: treat an unknown one as a blocker you cannot fix through the API.
    - `census_status` string, required: State of the AEAT census check for this NIF.
    - `has_default_series` boolean, required: Whether the NIF has a default document series to number with.
    - `fiscal_profile_complete` boolean, required: Whether the fiscal profile (tax id, address, territorial regime) is complete.
    - `operable` boolean, required: Whether the NIF is active and operable, as opposed to deactivated.
    - `missing_modules` string[], required: Modules the plan does not grant that issuing would need. Empty when nothing is missing.
    - `checked_at` string, date-time, required: Instant the verdict was computed (ISO 8601). It is a reading of a moment, not a stored flag.

## Other responses

- `400`: `parameter_unknown` with `subcode` `retired_active_profile_header`: the retired `X-Active-Profile` header was sent; the company goes in the path. `parameter_invalid_format` on `Factuarea-Version`: the header is not a `YYYY-MM-DD` date. `unsupported_api_version`: the `Factuarea-Version` date is not a supported version.
- `401`: Missing or invalid API key.
- `403`: The request is authenticated but not allowed: the API key lacks the required scope (`insufficient_scope`), the plan does not include the public API or this feature (`addon_not_active`, `feature_not_available_in_plan`), or the module is not available with a test key (`module_not_available_in_sandbox`).
- `404`: The requested resource does not exist or belongs to another company.
- `429`: Rate limit exceeded. Retry after the duration in `Retry-After`.
- `500`: Unexpected server error.

---

[API](https://skmtc.dev/factuarea/apis/factuarea-public-api.md) · [All operations](https://skmtc.dev/factuarea/apis/factuarea-public-api/llms.txt) · [OpenAPI document](https://skmtc.dev/factuarea/apis/factuarea-public-api/revisions/718e77934422?raw)