Log in Sign up →
Log in Sign up →

Request a Demo

What is Meta API ?

A tool making two (or more) APIs talking to each other and having the power to automate & monitor it!

 

Get Started

christopher-gower-m_HRfLhgABo-unsplash
concept_schema_3_5

 

Gain real-time visibility and govern APIs and integrations from one interface!

We believe in reverse productivity, developers should focus on creating values for their projects and businesses instead of wasting time on implementing protocols and doing some plumbing between APIs.

Plug

Connector

 
A connector is an API's endpoint implemented inside Meta API solution.

Whenever an API is added, all the endpoints are scanned and connectors are created for them.

A connector includes:

  • A specific interface for Oauth management and an easier usage

  • A typed response schema for code creation and edition based on connector's response

  • Monitoring on a specific schedule during execution to check for connector updates

Book

Spell

 
A Code EDITOR letting you write the logic needed for your integrations.

Once done, a Spell is exposed through an API endpoint that becomes its own API. We can also call a Spell a Meta-API 😉.

Key informations:

  • Code editor: a full Javascript/Typescript editor for writing your logic and mixing your algorithms with auto-generated code.
  • Dependencies: use NPM to add any JS/TS library inside a Spell
  • Releases: execute a live development inside the web editor and create new release to freeze your code and deploy it on different environment. A rollback is possible to switch back to previous version and change it in a snap
  • Logs: all requests are logged and you can access them accessible through a dedicated interface, filtering them by status, environment and Spells.

Meta Api_Wand_ Black    We choose to simplify all the boring stuff around API integration: authentication, schemas validation, monitoring, error management, etc. But without restraining available connectors (you can import your own) and writing your process with the same freedom as your own dev environment.    Meta Api_Wand_ Black

 

How can I use Meta-API?

 

Once you have created your Spell in your account, you have multiple way to start it.  Choose the method that fit your own requirements and processes:

Manual

We will expose a public and unique URL for each of your Spell.  You can safely share it with anyone on your team and trigger it from your web browser.

Examples:

  • Synchronize specific entries from your own database with your CRM

  • Clean duplicated entries on your CRM

Scheduled

You can schedule the execution of your Spell with a simple rule (like every 5 minutes) or on a more complex one (at 3:15 AM each Monday).

With the scheduled option, you can even define retry rules.  For example: "In case of a failure, retry after 3 min, 3 times max and with 5 min between each execution".

Examples:

  • Check for new invoices every day in Stripe, App Store and Google Play to report them onto a Google Spreadsheet

  • Report once a day all users' activity into our CRM

Webhook

Let other platform trigger your Spell for you:  you can rely on Webhooks to start your Spell.  Tools like Github, Trello, Hubspot support HTTP webhooks and you can configure them with your Spell's URL.  Each time an event will be launch, your Spell will received the associated payload and you are free to process it the way you want.

Examples:

  • Each time a new deal in Hubspot as been tagged as "Won", send a message into Slack to inform everyone

  • After each release published in Github, update the change log and Slack it to the whats-new channel

Integrated

A Spell is just a new API:  you can make request on it from any programming language and receive your custom response in a JSON

  • Once a user has signed up into our platform, trigger a Spell that will create his profile on Hubspot and send him a Welcome message

  • Each time a payment has been processed by our API, send a message on Slack to keep our sales time informed and email the account manager in case of a payment failure