REST endpoints

An endpoint stores a request: method, full URL, headers, query parameters, authentication and response/pagination settings. It can stand alone or use a business-system integration's authentication.

Configure a request

In Connections, choose the API option, name the endpoint and enter the intended method and URL. Configure authentication through the supported form fields. Basic and OAuth client-credential configurations are available where supported; other services may require explicit headers or a system-specific setup.

Do not assume ${secret_ref} in an arbitrary header is automatically substituted. Use the actual credential mechanism supported by your deployment and avoid committing credentials in endpoint examples or scripts.

Verify a read

Start with a small GET request. Inspect the upstream HTTP status, content type and actual body. POST /preview is a proxy operation: a successful DataMaker wrapper response does not by itself mean the upstream status was successful.

Check the response path used to select rows. An API might return an array directly or nest it inside items, data or another field. Configure pagination for the service's actual behavior, then verify more than one page. Use the endpoint pagination probe where available; do not assume every service supports an offset parameter.

Deliver rows

Confirm whether the target accepts one object, an array or a wrapped batch. Test the exact body with a small sample and inspect per-record errors. Request or grant the required approval before a governed load.

For larger deliveries, use a supported load job with key-map tracking. Retries must respect the target's idempotency behavior; an HTTP timeout can occur after the target accepted the write.

For SAP-specific metadata and CSRF behavior, use SAP OData.