# Get Started with Neobits

Neobits offers innovative financial technology solutions that simplify data gathering for banks and financial institutions. Our platform leverages cutting-edge technology to reduce integration complexity and costs.

Our technology stack includes secure API gateways, advanced data processing pipelines, and real-time analytics capabilities. We prioritize security, performance, and ease of use in all our offerings.

### Account Creation

❗

#### Account Creation

Accounts must be created with Neobits customer support.

To get started, please send an email to: [hello@neobits.no](mailto:hello@neobits.no)

### Our APIs

⚡

#### Core API

Handles authentication (OAuth 2.0 client credentials or basic auth) and administration of clients.

-   Supports OAuth 2.0 client credentials
-   Supports basic authentication
-   Comprehensive client administration
-   Secure token management

[Explore Core API Documentation →](https://docs.neobits.ai/api-reference/tag/core-authz.md)

⚡

#### Fuse API

Our innovative solution that connects disparate data sources into a unified, easy-to-consume format.

Learn more about Fuse's capabilities on our [website](https://neobits.ai/).

[Explore Fuse API Documentation →](https://docs.neobits.ai/api-reference/tag/fuse.md)

⚠️

#### Error Handling

Our APIs use consistent error codes and messages to help you handle errors gracefully.

[View Error Reference →](https://docs.neobits.ai/api-reference/errors.md)

### Rate Limits

Requests are rate limited per client IP address, currently at 10,000 requests per minute. A request over the limit gets 429 Too Many Requests with a Retry-After header: the number of seconds to wait before you retry. Retrying sooner only extends the wait.

Core answers in its OAuth 2.0 error format, with {"error":"too\_many\_requests","error\_code":"429-000"}. Fuse and Logic use the standard error format, with {"errors":\[{"name":"TooManyRequests","code":"429-000"}\]}. Because these requests never reach the API, the response has no timestamp, moreInfo or X-Request-ID.

Reuse access tokens until they expire instead of requesting a new token for every call. For a 429 without Retry-After, retry with exponential backoff and jitter.

### Retries and Idempotency

GET requests are safe to retry. Fuse inquiry creation and Logic executions and evaluations accept an Idempotency-Key header; any other retried POST is processed as a new request, so check whether the first attempt succeeded before you send it again.

The [Fuse](https://docs.neobits.ai/api-reference/tag/fuse.md#retries-and-idempotency) and [Logic](https://docs.neobits.ai/api-reference/tag/logic.md#handling-failures) introductions describe how their write operations behave when repeated.

### Versioning

Every API includes its major version in the path, for example /core/v1/oauth2/token, /logic/v1/deployments and /fuse/v2/inquiries. The exception is the discovery document and key set under /core/.well-known, which stay at the token issuer /core.

Changes, including deprecations, are listed in the release notes for [Core](https://docs.neobits.ai/api-reference/tag/core-authz/releases) and [Fuse](https://docs.neobits.ai/api-reference/tag/fuse/releases).

### Machine-Readable Docs

For code generators, API clients and AI coding agents:

-   The [OpenAPI 3.1 document](https://docs.neobits.ai/openapi.json) for every API, and one per API: [Core](https://docs.neobits.ai/openapi/core-authz.json), [Fuse](https://docs.neobits.ai/openapi/fuse.json) and [Logic](https://docs.neobits.ai/openapi/logic.json).
-   [llms.txt](https://docs.neobits.ai/llms.txt), an index of these docs in markdown, and [llms-full.txt](https://docs.neobits.ai/llms-full.txt) with every page in one file.
-   Every page as markdown: append .md to its URL, for example [/api-reference/get-started.md](https://docs.neobits.ai/api-reference/get-started.md).

### Next Steps

After creating your account, you can:

1.  Explore our API documentation
2.  Request access credentials
3.  Test the APIs in our sandbox environment
4.  Integrate with your systems