The new Jeto API Integrations offers a full range of products and services to assist your organization with the automation of a wide range of solutions. Here is an overview of the registration process and the solutions that are available to you.

Jeto API Specifications

Jeto RESTful API is build on OAS (Open API Standard) 3.0.

Registration

If you're just starting to explore the new Jeto API and have not completed your registration yet, please contact our support team or register here for the Jeto API Closed Beta Program and we'll get you all set up!

API Resources

Here is what you will get access to, after you signed up for the Jeto Intergations Beta:

  • Free access to the Jeto Beta Account: you will be granted access to a Jeto "sandbox" account that won't affect your Jeto production data. Once your account has been provisioned, you will receive an invite to as a "new" user.
    Access your Beta Account here.

  • Access to Jeto Swagger Hub. This developer technical resource is where you will access Jeto REST API Documentation as well as a professional development toolset to build and test your integrations.
    Access Jeto Swagger Hub here.

  • Free API Integration consulting workshop: our integration experts will conduct a discovery session with your team to analyse your needs recommend integration workflows and scope the API resources involved. This is Included as part of your Beta Onboarding sessions.

  • Access to Jeto Workato Connector (Beta). If you're using Workato and want to Add Jeto to one of your recipes, then this one is for you! Just let us know and we'll share the connector so that you can use it in your Recipes.

  • Coming Soon: Access to the Jeto Zapier Connector (Beta). If you're using Zapier and want to add Jeto to one of your Zaps, then this one is for you! Just let us know and we'll share the connector so that you can use it in your Zaps.

  • Developers technical support and API Feedback. Connect with us via Slack, online chat or email at help@jeto.io and we'll be happy to assist.

Configuration Requirements

The following configurations are recommended:

  • Jeto Beta Account should be synced to a Marketo Sandbox and\or restricted to a subset of test workspaces \ programs in order to prevent any issue with your Marketo Production instance while you are running integration experiments. Our team can assist your setup and to help minimize rework to implement your Integrations to production once it's ready.

  • A limited number of Launchers should be used for the your tests period. Once you have identified it, just let the Jeto support team know and we'll take care of replicating it for you in your Beta Account.

Jeto Integrations Overview - Options

Jeto API Integrations have been built to allow you to create a functional custom application or integration quickly and easily. We're offering 2 options to realize your integration projects.

1) Do it yourself: Jeto REST API License

The Jeto API License includes:

  • Jeto API feature and access to Documentation

  • Developer technical support

  • Workato Connector (Beta)

  • Coming Soon: Zapier Connector (Beta)


2) Do it for me: Integration Services

Don't have the time or the expertise configure your Workato or Jeto Connect Integration? Let our certified automation experts do it for you!


Note: The "Help me do it (faster)" / Jeto Connect option has been retired from the Beta Program and is unavailable at this time.

Please contact us via chat or email to learn more about pricing for these options.

Limitations and Future Improvements

These are the current limitations and known bugs that we have in the works.

  • Campaign Owner Default to API User: campaign owner now defaults to the logged in user (API user). We're updating the campaign Post and Put endpoints to control the value for the Owner and give the API the ability to create campaign on behalf of other users.

    Workaround: Run you testing using an Administrator Role, therefore you will be able to access all campaigns, Including the ones created from the API User.

    Fix: API Endpoints for Campaign Post and Put will be updated to add "Owner" as a parameter.

    Fix Status: In Progress

  • Campaigns and Campaign Draft Conversion: Campaign and Campaign Drafts currently exists as 2 distinct objects in Jeto and therefore have distinct IDs. Therefore If a Jeto Campaign Draft ID is stored in a 3rd party system, but later gets converted into a campaign, the ID will change and Draft object data will become outdated.

    Workaround: Consider skipping the Campaign Draft creation and tie your integration only to Jeto Campaigns (and not Campaign Drafts). This will make your integration work easier

    Fix: We will unify both objects and unify index keys to avoid these ID changes.

    Status: In Progress

  • Account wide access: API user is currently setup by creating a standard User and therefore will gain access to Objects (Campaigns, Launchers) that are shared with it. Unless you share these Launcher with the API user, your 3rd party system won't have visibility on it.

    Workaround: Don't forget to share Launcher with your API user.

    Fix: We're implementing M2M and a new scope for "Account wide" access permissions for API users.

    Status: In Progress

  • Paging and Sorting: Paging, Sorting and Search for Launcher, Campaigns, Users and Groups is currently performed in Jeto front-end but not available to the API.

    Workaround: Get request will return all results, you can use business logics on the client side to search of filter based on your specific needs.

    Fix: We're implementing paging, search, filter and sort using query parameters.

    Status: In Progress

  • Developer Portal: In addition to the Swagger Hub Specifications we're working on an improved Developer Portal experience,

Jeto API Lexicon

Jeto API: Application Programming Interface (API) is an interface that enables and defines interactions between Jeto and other software applications. It allows any 3rd party application to establish a machine-to-machine connection and Interact with Jeto without the need to use the Jeto Interface.

Jeto Connect: Powered by Workato, this Jeto feature brings iPAAS (integration platform as a services) capabilities to Jeto. It allows to build Integration to 3rd party Apps via a drag and drop interface to exchange data, and automate workflows with thousands of Apps, including Slack, Salesforce, Microsoft Dynamics, Asana, Jira, Workfront, Monday.com, Google Sheets, ERPs, CRMs and over a thousand more applications.

Apps: Any software application (typically vendor) with API capabilities that could potentially have a connection to jeto and be used in an integration (ex: Workfront, Asana, Jira, XTM Cloud, Salesforce)

Connector: Used in the context of IPAAS platforms (Worktato, Zapier, etc) a connector is a widget that contain a set of prebuilt functions to build an integration. Each connector includes a method of authentication, triggers, and actions for a specific app, allowing for a "fill in the blanks" approach to making API calls, as opposed to building your own custom actions from scratch. Connectors help save time and require less technical knowledge.

Connections: Authorized communication channel established between Jeto and an authenticated 3rd party application. Connections to Jeto require authorization access to be granted using OAuth2 access standard. Each Connection should correspond to one app combined with one set\scope of authorizations, and can be used in multiple workflows.

Integration: Solution that relies on a set of workflows to process the data exchange between 2 apps, according to a specific business goal and using connections as a secured communication channel.

Workflows: Set of steps defined by a web service (Jeto Connect, IPASS, Custom web application) that will get data flowing between your apps. For example, Jeto Connect offers many advanced workflow features, allowing it to handle bidirectional integration and automation scenarios, including complex data transformations, conditional triggers and actions, duplicate detection and much more.

Did this answer your question?