space-invoices-api

Name: space-invoices-api
Brand: space-invoices-api
Availability: InStock

★ Only Publicly Available OpenAPI DocumentPaymentsPayment ProcessingapiKey357 EndpointsREST

For Agents

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

Use for: I need to healthcontroller_getstatus, I want to healthcontroller_getstatus, Search for accountcontroller_getcount, Find all accountcontroller_list

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

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

Jentic One on Github View OpenAPI Document

Install Jentic One Beta

Connect the space-invoices-api to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the space-invoices-api, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fspaceinvoices.com%2Fspaceinvoices" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fspaceinvoices.com%2Fspaceinvoices" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with space-invoices-api.

HealthController_getStatus

AccountController_getCount

AccountController_list

DocumentPaymentIntentController_getPaymentIntentByShareableId

DocumentStripeConnectPaymentIntentController_getByShareableId

GET STARTED

Start building with space-invoices-api

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use space-invoices-api for, with concrete tasks.

★ 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.

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.

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.

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

Key Endpoints

357 endpoints — spaceinvoices.

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

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

Why Jentic?

What agents get from Jentic-routed access to this vendor.

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 isolation

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.

Intent-based discovery

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.

FAQs

Specific to using space-invoices-api through Jentic.

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.

space-invoices-api

Connect the space-invoices-api to your agent

Capabilities

Start building with space-invoices-api

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs