API Documentation

API Documentation

  • Common Usecases
  • Advanced Usecases
  • ZOOMstudio + ZOOMlibrary

›api.zoomcatalog.com/

About

  • Introduction
  • Conventions

Guides

    Common Usecases

    • Add ZOOMcatalogs to your website
    • Add customizable catalogs to your website
    • Add customizable flyers to your website

    Advanced Usecases

    • Add Linked ZOOMcatalogs AND customizable catalogs to your website on one page

    ZOOMstudio + ZOOMlibrary

    • Autologin for ZOOMstudio
    • Use ZOOMlibrary to Connect Your Product Data to ZOOMstudio

Endpoints

    api.zoomcatalog.com/

    • auth/authorize
    • auth/autologin
    • auth/register
    • catalogs/
    • catalogs/all
    • categories/
    • categories/all
    • categories/catalogs
    • custom/catalogs/
    • custom/catalogs/personalized
    • flyers/
    • flyers/personalized

    beta-library.zoomcatalog.com/

    • product-api

Resources

  • access_token
  • autologin_uri
  • catalogs_with_personalize
  • catalogs_without_personalize
  • category_descriptors
  • category_details
  • category_catalogs
  • custom_catalogs_with_actions
  • custom_catalogs_without_actions
  • Errors
  • flyers_with_actions
  • id
  • image
  • sample
  • subcompany
  • user_token
  • ZOOMcatalog_Client_ID
  • ZOOMcatalog_Client_Secret

Specifications

  • product
  • product/variations
  • product/variations/price_variance
  • product/media

https://api.zoomcatalog.com/auth/authorize

Intended Use

Retrieve the tokens required to populate the Authorization header for other ZOOMcatalog API Endpoints.

Return Types

access_token
user_token
error

Permitted HTTP Request Methods

POST

HTTP Request Headers

RequiredNameValue
YesContent-Type"application/json"

Parameters

RequiredNameValueLocation
Yesgrant_type"authorization_code"Request Body
Yesclient_id<ZOOMcatalog_Client_ID>Request Body
Yesclient_secret<ZOOMcatalog_Client_Secret>Request Body
Nofor_username<string>- unique identifier representing a user in your applicationRequest Body

Errors

CodeDescriptionLikely Cause
400Wrong format in HTTP body, MUST be a valid and well-form JSON stringThe POST body cannot be parsed into valid JSON
400Following arguments are required: [List of required arguments]One or more required parameters is missing
400for_username parameter cannot be emptyfor_username is present in the query string but has no value
400grant_type is not supportedThe POST body contains a grant_type other than "authorization_code"
403Invalid CLIENT SECRET, please contact the administratorThe <ZOOMcatalog_Client_Secret> is malformed or properly formed but invalid
404Invalid CLIENT_ID, please contact the administrator.The <ZOOMcatalog_Client_ID> is malformed or properly formed but invalid
500Description will varyError on the API Server

Examples

Here is an example curl request for getting a user token

curl https://api.zoomcatalog.com/auth/authorize -H 'Content-Type: application/json' -d '{"client_id": "CLIENT_ID_VALUE", "client_secret": CLIENT_SECRET", grant_type: GRANT_TYPE_VALUE}'

The response you will see:

{"user_token"" "USER_TOKEN_VALUE", "access_token": "ACCESS_TOKEN_VALUE"}

This user token generated needs to be used in the end-point to autologin uri

← Use ZOOMlibrary to Connect Your Product Data to ZOOMstudioauth/autologin →
  • Intended Use
  • Return Types
  • Permitted HTTP Request Methods
  • HTTP Request Headers
  • Parameters
  • Errors
  • Examples
ZOOMcatalog
Copyright © 2019 ZOOMcatalog