Develop with Oracle REST Data Services on Autonomous AI Database

Developing RESTful services is easy with the following development interfaces:

• Database Actions (SQL Developer Web): Use Database Actions on Autonomous AI Database to REST enable users. See Manage Users and User Roles on Autonomous AI Database - Connecting with Database Actions for more information.

• SQL Developer (desktop): With SQL Developer on your desktop, you can connect to your database and enable REST services access to tables and views, or develop custom RESTful Services based on your SQL and PL/SQL code. See Connect Oracle SQL Developer with a Wallet (mTLS) for more information.

• Oracle APEX: With APEX you can use the RESTful Services development pages to build and maintain your services and REST enabled objects. You can use the APEX SQL Workshop to access your Oracle RESTful Services and REST enabled objects. See How to Access RESTful Services for more information.

The Autonomous AI Database ADMIN account is REST Enabled. This allows for REST Services to be published in the ADMIN schemas and allows you to access Database Actions using the ADMIN database user account. Oracle recommends you create an application schema account for your RESTful Services and REST enabled objects. Services are secured using Database Authentication and your REST enabled schema.

The authenticated database user is only permitted access if the schema is REST enabled and the URL mapping for the request points to their own schema. A user is not authenticated when a request points to any other database schema. For example, the following request authenticated as the REST enabled schema HR is accessible:

GET /ords/hr/module/service/

However, when authenticated as the REST enabled schema SCOTT, the same request:

GET /ords/hr/module/service/

results in an error:

401 HTTP Unauthorized response/error

Any database user whose credentials are correct and meets these rules is authenticated and granted the ORDS, mid-tier, role: SQL Developer. The SQL Developer role enables the user to access any endpoint that requires the SQL Developer role.

See REST-Enable a Database Table in Quick Start Guide for information on how to enable a table for REST access.