API archive entry · source-reported
Developer documentation
# Welcome Implementing a new tool can be daunting, but it doesn't have to. You can implement journy.io in a few different ways to ensure it fits with the rest of your tech stack seamlessly. We welcome your feedback, ideas and suggestions. We really want to make your life easier, so if we’re falling short or should be doing something different, we want to hear about it. Send us an email at hi@journy.io or reach out via the chat on our website or on our platform. There are multiple ways you can send us data about users and accounts. We have both frontend and backend APIs, which can be used together at the same time. If you already use Segment, you can get up and running with journy.io in seconds. # Concepts ## Users The most basic entity is a user, a specific individual that completed an interaction with your product. We support multiple types of users, often differentiated by it's external ID prefix. E.g. In the case you are building an ordering app, there could easily be an administrator (who updates products and checks for orders) and the end-customers who place orders. One could have a typical ADM-XXXXXXXX ID, while the other would be referenced by USR-XXXXXXXXX. ## Accounts In B
Documentation & source
Use the provider’s reference for current endpoints, setup, limits and terms.
No separate documentation URL has been confirmed for this record.
Provider content retains its own terms. This listing does not grant reuse or training rights.
Access at a glance
These are reported access facts. Check the current documentation before integrating.
- Authentication: Unknown.
- HTTPS: not confirmed.
- Browser access (CORS): Unknown.
Pricing and limits
Current plans, quotas, and rate limits have not been reviewed for this listing. Check the provider’s current terms; no authentication does not necessarily mean free usage.
Documentation and sources
Imported from APIs.guru OpenAPI Directory. A detailed editorial review has not been published yet.
APIs.guru OpenAPI Directory · CC0 contributed definitions; upstream provider terms may differ
More Development APIs
1,000,000+ Recipe and Grocery List API (v2)
#Documentation This is the documentation for the partner endpoint of the BigOven Recipe and Grocery List API. The update brings with it Swagger-based documentation. Swagger is an emerging standard for describing REST-based APIs, and with this Swagger-compliant endpoint (above), you can make ready-to-go interface libraries for your code via swagger-codegen. For instance, it's easy to generate libraries for Node.js, Java, Ruby, ASP.NET MVC, jQuery, php and more! You can also try out the endpoint calls with your own api_key right here on this page. Be sure to enter your api_key above to use the "Try it out!" buttons on this page. ##Start Here Developers new to the BigOven API should start with this version, not with the legacy API. We'll be making improvements to this API over time, and doing only bug fixes on the v1 API. To pretend you're a BigOven user (for instance, to get your recently viewed recipes or your grocery list), you need to pass in Basic Authentication information in the header, just as with the v1 API. We do now require that you make all calls via https. You need to pass your api_key in with every call, though this can now be done on the header (send a request header "
Unknown · HTTPS unconfirmed · CORS Unknown
Account API
The Vonage Business Cloud Account API enables you to retrieve information about accounts. Your application must subscribe to the Provisioning API suite to use this API.
Unknown · HTTPS unconfirmed · CORS Unknown
Account API
Enables users to manage their Vonage API Account by programmable means. More information is available here: .
Unknown · HTTPS unconfirmed · CORS Unknown
Accounting API
Welcome to the Accounting API. You can use this API to access all Accounting API endpoints. ## Base URL The base URL for all API requests is `https://unify.apideck.com` We also provide a Mock API that can be used for testing purposes: `https://mock-api.apideck.com` ## Headers Custom headers that are expected as part of the request. Note that RFC7230 states header names are case insensitive. | Name | Type | Required | Description | | --------------------- | ------- | -------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------- | | x-apideck-consumer-id | String | Yes | The id of the customer stored inside Apideck Vault. This can be a user id, account id, device id or whatever entity that can have integration within your app. | | x-apideck-service-id | String | No | Describe the service you want to call (e.g., pipedrive). Only needed when a customer has activated multiple integrations for the same Unified API. | | x-apideck-raw | Boolean | No | Include raw response. Mostly used for debugging purposes. | | x-apideck-app-id | String | Yes | The application id of your Unify appli
Unknown · HTTPS unconfirmed · CORS Unknown
Accounts API
The Accounts API is a collection of methods used to query a customer account. It allows the developer to retrieve account-related data such as the user account balance. It should be noted that regional variations may exist - so some fields may not be returned for certain territories.
Unknown · HTTPS unconfirmed · CORS Unknown
Active Documentation for /v1
Our active docs provide the ability to test out your account and to see the responses to your queries. The services are RESTful, and are accessed using standard HTTP methods over a secure HTTPS channel. Requests and responses are currently sent in JSON format, and have a base URL of /v1.
Unknown · HTTPS unconfirmed · CORS Unknown
Source reference
This page separates source-reported facts from questions that need live provider verification.