API service URL in Jitterbit API Manager
Introduction
Custom APIs, OData services, and proxy APIs created through Jitterbit API Manager are accessed using an API's service URL. This page describes the parts of an API service URL.
An API's service URL is the URL used to consume the API using the configured authentication method.
The service URL may be called from an application or — if the API supports GET — you can paste the URL into a web browser to consume the API manually.
Format of an API service URL
All API service URLs follow the same format. Proxy APIs may have additional service path parameters:
<Protocol>://<Base URL>/<Environment URL Prefix>/<Version>/<Service Root>
<Protocol>://<Base URL>/<Environment URL Prefix>/<Version>/<Service Root>/<Service Path>
These are typical examples of an API's service URL:
https://JBExample123456.jitterbit.net/Development/1/customer
https://JBExample123456.jitterbit.net/Development/1/dog/pet/{petId}/uploadImage
Parts of an API service URL
Each API's service URL is automatically constructed of these parts:
Part | Example | Description |
---|---|---|
Protocol | https | The protocol is always https . |
Base URL | JBExample123456.jitterbit.net | The base URL. The default base URL consists of the Harmony organization name, Harmony organization ID, and Harmony region domain name:
To use a custom domain name as the base URL for your published APIs, you can use one of these methods:
|
Harmony Organization Name | JBExample | The name of the Harmony organization. For trial licenses that were initiated prior to the 10.64 / 11.2 release, the organization name is appended with the word |
Harmony Organization ID | 123456 | The Harmony organization ID. |
Harmony Region Domain Name | jitterbit.net | The Harmony region domain name of the Harmony organization:
|
Environment URL Prefix | Development | The URL Prefix specified in the configuration of the environment where the API is being configured (see the field URL prefix in Environments). |
Version | 1 | The Version specified in the configuration of the custom API, OData service, or proxy API in these steps: |
Service Root | customerdog | The Service Root specified in the configuration of the custom API, OData service, or proxy API in these steps: |
Service Path (proxy API only) | pet/{petId}/uploadImage | The Path specified in the configuration of the proxy API in this step: |