Tier: Scribe Created and supported by Scribe. Created and supported by a Scribe partner and were certified by Scribe to be compatible with the Scribe platform. Created by members of the Scribe community (Scribe users or Scribe Labs), but have not been productized. They are made available on an "as is" basis to provide samples of what connectivity can be created for our platforms. Scribe does not offer formal support for these connectors.
Works with: Scribe Online
How to Download: Marketplace
Representational State Transfer (REST) is an architectural style that has become the dominant approach for constructing web APIs. REST consists of a set of guidelines or constraints. It is not a standard, which makes it difficult to say for sure whether an API is RESTful or not. Until recently there was no standard way to describe a RESTful API and therefore no standard way to connect to one. Connecting meant coding, but that has changed.
The OpenAPI Specification (aka Swagger 2.0) provides a uniform description of RESTful APIs that machines can read and understand. Scribe’s REST Connector reads an API definition in an OpenAPI Specification document to understand how to interact with a RESTful API, including authentication and discovery of metadata and operations.
If you use a cloud application that offers an OpenAPI Specification for its API, the REST Connector can connect directly to it without coding a custom connector. Simply import the OpenAPI Specification into the connection definition, and Scribe does the rest. That isn’t the only scenario, however.
As part of their digital transformation initiatives, many enterprises are adding a REST API layer on top of legacy applications using API Management tools. Most of these tools provide OpenAPI Specifications for the new APIs. This allows the REST Connector to interact with legacy applications. With Scribe Online, you can integrate legacy ERP, HR or other applications with cloud applications like Salesforce, Dynamics 365 and Marketo.
Even if the application you want to connect has no OpenAPI Specification, you can write your own for use with the REST Connector.
- Connect to RESTful APIs using an OpenAPI Specification
- Authentication methods: none, basic, API key or OAuth 2.0 Client Credentials Grant
- Supports standard REST operations: GET, POST, PUT and DELETE
- Works with on-premise and cloud agents