canonical: https://jentic.com/apis/spaceinvoices.com/spaceinvoices

# space-invoices-api

spaceinvoices.com/main version 2.0.0. The API exposes 357 endpoints secured with apiKey authentication.

## For AI agents

Programmatically healthcontroller_getstatus, healthcontroller_getstatus. Covers 357 operations with apiKey authentication.

## Scope

Does not handle communications, crm, or developer tools - use for payments only.

## Capabilities

- HealthController_getStatus
- AccountController_getCount
- AccountController_list
- DocumentPaymentIntentController_getPaymentIntentByShareableId
- DocumentStripeConnectPaymentIntentController_getByShareableId
- FatturaPaController_createWebhooksSubscription

## Use cases

### Payments Operations

Use the space-invoices-api to perform payments operations programmatically. The API provides 357 endpoints covering core functionality including healthcontroller_getstatus, healthcontroller_getstatus, accountcontroller_getcount.

Example prompt: Call GET /live to healthcontroller_getstatus

### Automated Organization Management

Automate organization operations by combining multiple space-invoices-api endpoints. Agents can healthcontroller_getstatus and then accountcontroller_getcount in a single workflow.

Example prompt: Call GET /ready to healthcontroller_getstatus, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call space-invoices-api endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.

Example prompt: Search Jentic for 'healthcontroller_getstatus', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/live` | HealthController_getStatus |
| GET | `/ready` | HealthController_getStatus |
| GET | `/v1/accounts/count` | AccountController_getCount |
| GET | `/v1/accounts` | AccountController_list |
| GET | `/v1/documents/{shareableId}/payment-intent` | DocumentPaymentIntentController_getPaymentIntentByShareableId |
| GET | `/v1/documents/{shareableId}/stripe-connect/payment-intent` | DocumentStripeConnectPaymentIntentController_getByShareableId |
| POST | `/v1/fattura-pa/webhooks` | FatturaPaController_createWebhooksSubscription |
| POST | `/v1/organizations/{organizationId}/atcud/get-active` | AtcudSeriesController_getActiveAtcud |

## Key resources

- **Organization** — Operations related to Organization
- **Document** — Operations related to Document
- **Account** — Operations related to Account
- **AtcudSeries** — Operations related to AtcudSeries
- **Unit** — Operations related to Unit

## Why Jentic

- **Setup:** Wiring Space Invoices by hand means passing your API key as an Authorization header or access_token query param, then routing across hundreds of account, organization, and document operations yourself. Through Jentic you install once, import the Space Invoices API from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** Space Invoices puts the organization id in the URL path (`/v1/organizations/{organizationId}/...`), so a rule can pin your agent to one organization: it can work within that organization and nothing else. You choose the operations it may call, so it only touches the accounts, documents, or organization data you allow.
- **Credential handling:** Your Space Invoices API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'list accounts' or 'get a document payment intent', and Jentic returns the matching Space Invoices operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Stripe** — Alternative payments API
- **Adyen** — Alternative payments API
- **Square** — Complementary payments API
- **Paypal** — Complementary payments API

## FAQ

### What authentication does the space-invoices-api use?

The space-invoices-api uses an API key passed in the `Authorization` header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I healthcontroller_getstatus with the space-invoices-api?

Yes. Use the GET /live endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the space-invoices-api?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I healthcontroller_getstatus through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'healthcontroller_getstatus'. Jentic returns the matching space-invoices-api operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the space-invoices-api have?

The space-invoices-api exposes 357 endpoints covering organization, document, account operations.

### Can I limit what my agent is allowed to do with the Space Invoices API?

Yes. Because you run Jentic One yourself, your own rules decide which Space Invoices operations and credentials the agent may use. Since Space Invoices puts the organization id in the URL path, such as `/v1/organizations/{organizationId}/atcud/get-active`, you can pin the agent to a single organization so it cannot touch any other. You also choose exactly which operations it may call, for example allowing it to list accounts via GET `/v1/accounts` or read a document payment intent while blocking everything else.