Oracle REST Data Services API

Name: Oracle REST Data Services API API
Brand: Oracle REST Data Services API
Availability: InStock

✓ Official Vendor SpecStorageDatabasebasic, oauth2, bearer51 EndpointsREST

For Agents

Query Oracle Database tables and views over REST, call custom ORDS resource modules, and manage ORDS OAuth2 clients and database administration endpoints.

Connect the Oracle REST Data Services API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Oracle REST Data Services 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.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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 Oracle REST Data Services API API.

Query and modify rows in Oracle Database tables exposed via AutoREST

Retrieve a single row from a schema object by primary key

Batch-load rows into a schema object through the batchload endpoint

Invoke custom resource modules backed by SQL or PL/SQL handlers

GET STARTED

Start building with Oracle REST Data Services API API

Explore with Jentic

View OpenAPI Document

Oracle REST Data Services (ORDS) provides a REST interface to an Oracle Database, exposing tables and views as resources, hosting custom resource modules backed by SQL or PL/SQL handlers, and serving administrative endpoints for the database itself. It supports AutoREST for instant CRUD over schema objects, OpenAPI catalog generation, OAuth2 client management, and database environment introspection. ORDS sits between application code and the database, removing the need for a separate middle tier for many read and write paths.

Use Cases

Patterns agents use Oracle REST Data Services API API for, with concrete tasks.

★ Database-Backed Microservice Without a Middle Tier

Expose Oracle tables and views directly to a microservice through ORDS AutoREST instead of building a separate Java or Node service. The service consumes /{schema}/{object}/ endpoints for list and create and /{schema}/{object}/{id} for get and update, with consistent paging and filtering provided by ORDS.

GET /{schema}/{object}/ with query filters to page through rows, then PUT /{schema}/{object}/{id} to update the matching record

Bulk Ingest into Oracle from External Pipelines

Use ORDS batchload to push large numbers of records from an external pipeline into Oracle without juggling JDBC drivers or running PL/SQL on a scheduled job. The batchload endpoint accepts payloads tuned for high-volume insert and is idempotent on the underlying object key.

POST /{schema}/{object}/batchload with a multi-row payload from the upstream pipeline

Custom Resource Modules for Domain APIs

Expose business logic stored as PL/SQL packages or hand-tuned SQL through ORDS resource modules with /{schema}/{module}/{templatePath} URLs. This is how teams build domain-specific Oracle APIs without adding a separate application tier on top of the database.

GET /{schema}/{module}/{templatePath} to invoke the PL/SQL handler that serves a domain-specific report

Database Operations and Health Checks

Operations teams can probe the Oracle Database environment, status, and configuration through the ORDS administration endpoints under /admin/_/db-api/stable. This pattern fits health dashboards and runbook automation that need to confirm a database is reachable and healthy without a SQL*Plus session.

GET /admin/_/db-api/stable/database/status from the ops dashboard every 60 seconds

Agent-Driven Oracle Database Access via Jentic

An AI assistant for application teams can query and update Oracle tables through ORDS without holding raw database credentials. Jentic resolves natural-language intents like 'list orders for customer 123' to the right AutoREST or resource-module endpoint and executes against the configured ORDS instance.

Search Jentic for 'query an Oracle table by id', load the GET /{schema}/{object}/{id} operation, and execute against the ORDS instance

Key Endpoints

51 endpoints — oracle rest data services (ords) provides a rest interface to an oracle database, exposing tables and views as resources, hosting custom resource modules backed by sql or pl/sql handlers, and serving administrative endpoints for the database itself.

METHOD

PATH

DESCRIPTION

GET

/{schema}/{object}/

List rows from a schema object

GET

/{schema}/{object}/{id}

Retrieve a row by primary key

POST

/{schema}/{object}/batchload

Batch load rows into a schema object

GET

/admin/_/db-api/stable/database/status

Get database status

GET

/admin/_/db-api/stable/database/environment

Get database environment metadata

GET

/admin/_/db-api/stable/metadata-catalog/

Retrieve the metadata catalog

GET

/{schema}/{object}/

List rows from a schema object

GET

/{schema}/{object}/{id}

Retrieve a row by primary key

POST

/{schema}/{object}/batchload

Batch load rows into a schema object

GET

/admin/_/db-api/stable/database/status

Get database status

GET

/admin/_/db-api/stable/database/environment

Get database environment metadata

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

ORDS Basic Auth, OAuth2 client, and Bearer credentials are stored encrypted in the Jentic vault per ORDS instance. Agents authenticate with a scoped Jentic session and never see the raw database or OAuth secrets.

Intent-based discovery

Agents search by intent like 'query an Oracle table' or 'batch load records into Oracle', and Jentic returns the matching AutoREST or resource-module endpoint with its parameter schema.

Time to first call

Direct ORDS integration: 1-2 days to wire up auth, REST-enable target schema objects, and handle pagination. Through Jentic: under 1 hour from signup to first table read or write.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Supabase REST API

PostgREST-style auto-generated REST over Postgres rather than Oracle Database

Pick Supabase for greenfield Postgres-backed services; ORDS is the right choice when the system of record is Oracle Database.

Alternative

MongoDB Atlas Data API

Document-database REST API with a different data model than Oracle's relational tables

Use MongoDB Atlas Data API when the data is document-shaped; pick ORDS when the data lives in Oracle relational schemas.

Complementary

Snowflake SQL API

Cloud data warehouse SQL API often paired with Oracle for analytics offload

Use Snowflake for analytical workloads on warehoused data; ORDS handles the operational reads and writes against the Oracle source.

FAQs

Specific to using Oracle REST Data Services API API through Jentic.

What authentication does the Oracle REST Data Services API use?

The spec declares Basic Auth, OAuth2, and Bearer token schemes. Production deployments typically use OAuth2 client credentials issued by ORDS, with Basic Auth available for administrative endpoints. Through Jentic, whichever credential type you configure is held encrypted in the vault and the agent only sees a scoped session.

Can I expose any Oracle table as REST through this API?

Tables and views need to be REST-enabled in ORDS first (using ORDS.ENABLE_OBJECT in the database). Once enabled, /{schema}/{object}/ and /{schema}/{object}/{id} provide list, get, insert, update, and delete operations through AutoREST. The batchload endpoint covers bulk inserts.

What is a resource module in ORDS?

A resource module is a named collection of REST endpoints backed by SQL or PL/SQL handlers, addressed at /{schema}/{module}/{templatePath}. This is how teams ship domain-specific Oracle APIs without adding a separate application tier.

What are the rate limits for the Oracle REST Data Services API?

ORDS does not impose vendor-side rate limits — the API runs on customer-managed infrastructure. Practical throughput depends on the database and the ORDS server tier. Use connection pool sizing, table-level statistics, and Oracle's own resource manager rather than relying on API rate limits.

Does ORDS publish an OpenAPI catalog of its endpoints?

Yes. /admin/_/db-api/stable/metadata-catalog/ returns a metadata catalog and ORDS can generate OpenAPI documents for resource modules. This lets clients introspect available paths without checking the database configuration directly.

How do I query an Oracle table through Jentic?

Install the SDK with pip install jentic, then search for 'query an Oracle table by id'. Jentic returns the GET /{schema}/{object}/{id} operation; load it, supply the schema, object, and id, and execute. Sign up at https://app.jentic.com/sign-up.