Scribe Gives Integration Developers Greater Control with Expanded API Capabilities
July 07, 2016

Scribe Software announced a number of significant additions to the REST application programming interface (API) for Scribe Online, the company’s integration platform as a service (iPaaS).

These new features dramatically expand the scope of the API, giving SaaS providers, SIs, and enterprises far greater ability to embed integrations into applications and accelerating the development of custom integrations for their customers and/or users.

“Virtually every business application becomes more valuable to its users when it is tied to other systems and data sources through a reliable, configured integration,” said Shawn McGowan, CEO at Scribe. “The expanded Scribe Online API allows developers to embed our iPaaS capabilities into their applications much more easily so they can develop connected processes with less effort than ever before and easily tailor the integration to the unique needs of every deployment.”

Scribe’s new API offers these critical new capabilities:

- Loading metadata for Connections: An application can use this API call to get immediate access to comprehensive metadata from a target application, including what entities, fields, and relationships are exposed through Scribe Online for an integration project. Since the metadata also includes information about custom objects, entities, and relationships, this call allows an application to easily discover the unique aspects of a configured application, such as custom objects in a Salesforce instance. The information is provided in a standard form for all applications in Scribe’s marketplace, eliminating the need for solution developers to learn the unique aspects of each application’s API. This call, therefore, accelerates integration projects and eliminates the need to maintain a large staff of developers to track API changes for specific applications.

- Creating, updating, and deleting Basic and Advanced Integration Maps: With this capability, an application can change or customize data mappings based on the metadata of the target application. Because the metadata describes how an application has been uniquely configured, this API call allows organizations to develop custom integrations at scale – shortening the time to create integrations that are customized for a unique application configuration.

The expanded API adheres to the principles of RESTful Web services and is part of the Scribe Toolkit, along with the Fast Connector Framework and the Connector Development Kit. The Toolkit is for developers that want to add new connectivity endpoints to the Scribe Online iPaaS or want to interact directly with the platform from within their own or industry-leading applications or cloud services.

Additional highlights of Scribe’s API include the ability to:

- Easily implement both Integration and Replication Solutions, including custom data mappings which provide verbose validation.

- Provision integrations for customers including the ability to install connectors and both cloud and on-premises agents.

- Configure Scribe’s pre-built application connectors to retrieve metadata and custom objects which can be used to create customized data mappings.

- Run and schedule integrations.

- Monitor and manage an integration throughout its lifecycle using information on the status of the integration, a detailed execution history, and performance data such as records that have been processed.

- Create and delete child organizations under a parent organization.

The Latest

September 18, 2017

Web development and web design are intertwined in such a way that there is not one without the other — not anymore at least. The following outlines 5 benefits of collaboration ...

September 14, 2017

Mastering modern software development by building a "Modern Software Factory" is at the heart of business success in the digital economy, according to the results of a survey of over 1,200 IT leaders released today by CA Technologies ...

September 13, 2017

IT-Business convergence is needed to deliver continuous change, but many of the current tools add complexity and fail to merge the two, according to the Panaya 2017 State of Functional Testing Report ...

September 11, 2017

Application Program Interfaces (API’s) represent an effective way to build and manage mobile services. By using APIs — a set of routines, protocols and tools for building software applications — application developers no longer have to buy technology software or hardware. Instead, they can simply plug into a growing open ecosystem of API-driven services. It is simple to integrate, and saves time and money for new developers ...

September 07, 2017

More than a quarter of enterprises globally have not built, customized or virtualized any mobile apps in the last 12 months, according to the latest mobile app survey by Gartner ...

September 06, 2017

The number of malware breaches (to use a generic term) are rising in near exponential numbers and, unless there are radical changes, this is set to continue unabated. Most pundits agree with this forecast ...

September 01, 2017

DevOps encourages communication and collaboration between development and operations teams. Achieving greater synergies between the Dev and Ops teams doesn't happen overnight, but it is possible to fast track the process with the right technologies in place. One such technology is IT automation ...

August 29, 2017

Newly released data shows that distributed denial of service (DDoS) and web application attacks are on the rise once again, according to the Second Quarter, 2017 State of the Internet / Security Report released by Akamai Technologies ...

August 28, 2017

Organizations that are actively managing the quality of open source components flowing into production applications are realizing a 28 percent improvement in developer productivity, a 30 percent reduction in overall development costs, and a 48 percent increase in application quality, according to the 2017 State of the Software Supply Chain Report from Sonatype ...

August 24, 2017

Being able to deploy distinct code elements quickly, matched with the ability to deploy the next release version or the previous version, facilitates moving forward, even on failure. The small program unit minimizes the production impact upon failure — maybe only a few people experience the problem instead of a large set of application users when large code deployments go wrong. Besides implementing small code segments, there are two additional reasons why fail forward has proven successful: continuous integration and testing ...

Share this