Service Management API.json

{
  "basePath": "",
  "swaggerVersion": "0.1a",
  "apiVersion": "1.0",
  "apis": [
    {
      "path": "/transactions/authorize.xml",
      "format": "xml",
      "operations": [
        {
          "httpMethod": "GET",
          "summary": "Authorize (App Id authentication pattern)",
          "description": "<p>Read-only operation to authorize an application in the App Id authentication pattern. <p>It is used to check if a particular application exists, is active and is within its usage limits. It can be optionally used to authenticate a call using an application key. It's possible to pass a 'predicted usage' to the authorize call. This can serve three purposes:<p>1) To make sure an API call won't go over the limits before the call is made, if the usage of the call is known in advance. In this case, the estimated usage can be passed to the authorize call, and it will respond whether the actual API call is still within limit. <p>2) To limit the authorization only to a subset of metrics. If usage is passed in, only the metrics listed in it will be checked against the limits. For example: There are two metrics defined: <em>searches</em> and <em>updates</em>. <em>updates</em> are already over limit, but <em>searches</em> are not. In this case, the user should still be allowed to do a search call, but not an update one. And, <p>3) If no usage is passed then any metric with a limit exceeded state will result in an _authorization_failed_ response.<p><b>Note:</b> Even if the predicted usage is passed in, authorize is still a <b>read-only</b> operation. You have to make the report call to report the usage. <p>The response can have an http response code: <code class='http'>200</code> OK (if authorization is granted), <code class='http'>409</code> (if it's not granted, typically application over limits or keys missing, check 'reason' tag),  or <code class='http'>403</code> (for authentication errors, check 'error' tag) and <code class='http'>404</code> (not found).",
          "group": "authorize",
          "parameters": [
            {
              "name": "service_token",
              "dataType": "string",
              "required": true,
              "paramType": "query",
              "threescale_name": "service_tokens",
              "description": "Your service api key with 3scale (also known as service token)."
            },
            {
              "name": "service_id",
              "dataType": "string",
              "required": true,
              "paramType": "query",
              "threescale_name": "service_ids",
              "description": "Service id. Required."
            },
            {
              "name": "app_id",
              "dataType": "string",
              "required": true,
              "paramType": "query",
              "threescale_name": "app_ids",
              "description": "App Id (identifier of the application if the auth. pattern is App Id)"
            },
            {
              "name": "app_key",
              "dataType": "string",
              "required": false,
              "paramType": "query",
              "threescale_name": "app_keys",
              "description": "App Key (shared secret of the application if the authentication pattern is App Id). The app key is required if the application has one or more keys defined."
            },
            {
              "name": "referrer",
              "dataType": "string",
              "required": false,
              "paramType": "query",
              "description": "Referrer IP Address or Domain. Required only if referrer filtering is enabled. If special value '*' (wildcard) is passed, the referrer check is bypassed."
            },
            {
              "name": "usage",
              "dataType": "hash",
              "required": false,
              "paramType": "query",
              "allowMultiple": false,
              "description": "Predicted Usage. Actual usage will need to be reported with a report or an authrep.",
              "parameters": [
                {
                  "name": "metric",
                  "dataType": "custom",
                  "required": false,
                  "paramType": "query",
                  "allowMultiple": true,
                  "threescale_name": "metric_names",
                  "description": "Metric to be reported"
                }
              ]
            }
          ]
        }
      ]
    },
    {
      "path": "/transactions/authorize.xml",
      "format": "xml",
      "operations": [
        {
          "httpMethod": "GET",
          "tags": [
            "authorize",
            "user_key"
          ],
          "nickname": "authorize_user_key",
          "deprecated": false,
          "summary": "Authorize (API Key authentication pattern)",
          "description": "Read-only operation to authorize an application in the App Key authentication pattern. <p>It is used to check if a particular application exists, is active and is within its usage limits. It can be optionally used to authenticate a call using an application key. It's possible to pass a 'predicted usage' to the authorize call. This can serve three purposes:<p>1) To make sure an API call won't go over the limits before the call is made, if the usage of the call is known in advance. In this case, the estimated usage can be passed to the authorize call, and it will respond whether the actual API call is still within limit. <p>2) To limit the authorization only to a subset of metrics. If usage is passed in, only the metrics listed in it will be checked against the limits. For example: There are two metrics defined: <em>searches</em> and <em>updates</em>. <em>updates</em> are already over limit, but <em>searches</em> are not. In this case, the user should still be allowed to do a search call, but not an update one. And, <p>3) If no usage is passed then any metric with a limit exceeded state will result in an _authorization_failed_ response.<p><b>Note:</b> Even if the predicted usage is passed in, authorize is still a <b>read-only</b> operation. You have to make the report call to report the usage. <p>The response can have an http response code: <code class='http'>200</code> OK (if authorization is granted), <code class='http'>409</code> (if it's not granted, typically application over limits or keys missing, check 'reason' tag),  or <code class='http'>403</code> (for authentication errors, check 'error' tag) and <code class='http'>404</code> (not found).",
          "group": "authorize",
          "parameters": [
            {
              "name": "service_token",
              "dataType": "string",
              "required": true,
              "paramType": "query",
              "threescale_name": "service_tokens",
              "description": "Your service api key with 3scale (also known as service token)."
            },
            {
              "name": "service_id",
              "dataType": "string",
              "required": true,
              "paramType": "query",
              "threescale_name": "service_ids",
              "description": "Service id. Required."
            },
            {
              "name": "user_key",
              "dataType": "string",
              "required": true,
              "paramType": "query",
              "theescale_name": "user_keys",
              "description": "User Key (identifier and shared secret of the application if the auth. pattern is Api Key)"
            },
            {
              "name": "referrer",
              "dataType": "string",
              "required": false,
              "paramType": "query",
              "description": "Referrer IP Address or Domain. Required only if referrer filtering is enabled. If special value '*' (wildcard) is passed, the referrer check is bypassed."
            },
            {
              "name": "usage",
              "dataType": "hash",
              "required": false,
              "paramType": "query",
              "allowMultiple": false,
              "description": "Predicted Usage. Actual usage will need to be reported with a report or an authrep.",
              "parameters": [
                {
                  "name": "metric",
                  "dataType": "custom",
                  "required": false,
                  "paramType": "query",
                  "allowMultiple": true,
                  "threescale_name": "metric_names",
                  "description": "Metric to be reported"
                }
              ]
            }
          ]
        }
      ]
    },
    {
      "path": "/transactions/oauth_authorize.xml",
      "format": "xml",
      "operations": [
        {
          "httpMethod": "GET",
          "tags": [
            "authorize",
            "user_key"
          ],
          "nickname": "oauth_authorize",
          "deprecated": false,
          "summary": "Authorize (OAuth authentication mode pattern)",
          "description": "<p>Read-only operation to authorize an application in the OAuth authentication pattern.<p>When using this endpoint please pay attention at your handling of app_id and app_key parameters. If you don't specify an app_key, the endpoint assumes the app_id specified has already been authenticated by other means. If you specify the app_key parameter, even if it is empty, it will be checked against the application's keys. If you don't trust the app_id value you have, use app keys and specify one.<p>This call returns extra data (secret and redirect_url) needed to power OAuth APIs. It's only available for users with OAuth enabled APIs. <p>It is used to check if a particular application exists, is active and is within its usage limits. It can be optionally used to authenticate a call using an application key. It's possible to pass a 'predicted usage' to the authorize call. This can serve three purposes:<p>1) To make sure an API call won't go over the limits before the call is made, if the usage of the call is known in advance. In this case, the estimated usage can be passed to the authorize call, and it will respond whether the actual API call is still within limit. <p>2) To limit the authorization only to a subset of metrics. If usage is passed in, only the metrics listed in it will be checked against the limits. For example: There are two metrics defined: <em>searches</em> and <em>updates</em>. <em>updates</em> are already over limit, but <em>searches</em> are not. In this case, the user should still be allowed to do a search call, but not an update one. And, <p>3) If no usage is passed then any metric with a limit exceeded state will result in an _authorization_failed_ response.<p><b>Note:</b> Even if the predicted usage is passed in, authorize is still a <b>read-only</b> operation. You have to make the report call to report the usage. <p>The response can have an http response code: <code class='http'>200</code> OK (if authorization is granted), <code class='http'>409</code> (if it's not granted, typically application over limits or keys missing, check 'reason' tag),  or <code class='http'>403</code> (for authentication errors, check 'error' tag) and <code class='http'>404</code> (not found).",
          "group": "authorize",
          "parameters": [
            {
              "name": "service_token",
              "dataType": "string",
              "required": true,
              "paramType": "query",
              "threescale_name": "service_tokens",
              "description": "Your service api key with 3scale (also known as service token)."
            },
            {
              "name": "service_id",
              "dataType": "string",
              "required": true,
              "paramType": "query",
              "threescale_name": "service_ids",
              "description": "Service id. Required."
            },
            {
              "name": "app_id",
              "dataType": "string",
              "required": false,
              "paramType": "query",
              "threescale_name": "app_ids",
              "description": "Client Id (identifier of the application if the auth. pattern is OAuth, note that client_id == app_id)"
            },
            {
              "name": "app_key",
              "dataType": "string",
              "required": false,
              "paramType": "query",
              "threescale_name": "app_keys",
              "description": "App Key (shared secret of the application). The app key, if present, must match a key defined for the application. Note that empty values are considered invalid."
            },
            {
              "name": "referrer",
              "dataType": "string",
              "required": false,
              "paramType": "query",
              "description": "Referrer IP Address or Domain. Required only if referrer filtering is enabled. If special value '*' (wildcard) is passed, the referrer check is bypassed."
            },
            {
              "name": "usage",
              "dataType": "hash",
              "required": false,
              "paramType": "query",
              "allowMultiple": false,
              "description": "Predicted Usage. Actual usage will need to be reported with a report or an authrep.",
              "parameters": [
                {
                  "name": "metric",
                  "dataType": "custom",
                  "required": false,
                  "paramType": "query",
                  "allowMultiple": true,
                  "threescale_name": "metric_names",
                  "description": "Metric to be reported"
                }
              ]
            },
            {
              "name": "redirect_url",
              "dataType": "string",
              "required": false,
              "paramType": "query",
              "description": "Optional redirect URL for OAuth. Will be validated if sent."
            },
            {
              "name": "redirect_uri",
              "dataType": "string",
              "required": false,
              "paramType": "query",
              "description": "Optional redirect URI for OAuth. This is the same as 'redirect_url', but if used you should expect a matching 'redirect_uri' response field."
            }
          ]
        }
      ]
    },
    {
      "path": "/transactions/authrep.xml",
      "format": "xml",
      "operations": [
        {
          "httpMethod": "GET",
          "summary": "AuthRep (Authorize + Report for the App Id authentication pattern)",
          "description": "<p>Authrep is a <b>'one-shot'</b> operation to authorize an application and report the associated transaction at the same time.<p>The main difference between this call and the regular authorize call is that usage will be reported if the authorization is successful. Authrep is the most convenient way to integrate your API with the 3scale's Service Manangement API since it does a 1:1 mapping between a request to your API and a request to 3scale's API.<p>If you do not want to do a request to 3scale for each request to your API or batch the reports you should use the Authorize and Report methods instead.<p>Authrep is <b>not a read-only</b> operation and will increment the values if the authorization step is a success.",
          "group": "authrep",
          "parameters": [
            {
              "name": "service_token",
              "dataType": "string",
              "required": true,
              "paramType": "query",
              "threescale_name": "service_tokens",
              "description": "Your service api key with 3scale (also known as service token)."
            },
            {
              "name": "service_id",
              "dataType": "string",
              "required": true,
              "paramType": "query",
              "threescale_name": "service_ids",
              "description": "Service id. Required."
            },
            {
              "name": "app_id",
              "dataType": "string",
              "required": true,
              "paramType": "query",
              "threescale_name": "app_ids",
              "description": "App Id (identifier of the application if the auth. pattern is App Id)"
            },
            {
              "name": "app_key",
              "dataType": "string",
              "required": false,
              "paramType": "query",
              "threescale_name": "app_keys",
              "description": "App Key (shared secret of the application if the authentication pattern is App Id). The app key is required if the application has one or more keys defined."
            },
            {
              "name": "referrer",
              "dataType": "string",
              "required": false,
              "paramType": "query",
              "description": "Referrer IP Address or Domain. Required only if referrer filtering is enabled. If special value '*' (wildcard) is passed, the referrer check is bypassed."
            },
            {
              "name": "usage",
              "dataType": "hash",
              "required": false,
              "paramType": "query",
              "allowMultiple": false,
              "description": "Usage will increment the metrics with the values passed. The value can be only a positive integer (e.g. 1, 50). Reporting usage[hits]=1 will increment the hits counter by +1.",
              "parameters": [
                {
                  "name": "metric",
                  "dataType": "custom",
                  "required": false,
                  "paramType": "query",
                  "allowMultiple": true,
                  "threescale_name": "metric_names",
                  "description": "Metric to be reported"
                }
              ]
            },
            {
              "name": "log",
              "dataType": "hash",
              "required": false,
              "paramType": "query",
              "allowMultiple": false,
              "description": "Request Log allows to log status codes of your API back to 3scale to maintain a log of the latest activity on your API. Request Logs are optional and not available in all 3scale plans.",
              "parameters": [
                {
                  "name": "code",
                  "dataType": "string",
                  "paramType": "query",
                  "description_inline": true,
                  "description": "Response code of the response from your API (needs to be URL encoded). Optional. Truncated after 32bytes."
                }
              ]
            }
          ]
        }
      ]
    },
    {
      "path": "/transactions/authrep.xml",
      "format": "xml",
      "operations": [
        {
          "httpMethod": "GET",
          "summary": "AuthRep (Authorize + Report for the API Key authentication pattern)",
          "description": "<p>Authrep is a <b>'one-shot'</b> operation to authorize an application and report the associated transaction at the same time.<p>The main difference between this call and the regular authorize call is that usage will be reported if the authorization is successful. Authrep is the most convenient way to integrate your API with the 3scale's Service Manangement API since it does a 1:1 mapping between a request to your API and a request to 3scale's API.<p>If you do not want to do a request to 3scale for each request to your API or batch the reports you should use the Authorize and Report methods instead.<p>Authrep is <b>not a read-only</b> operation and will increment the values if the authorization step is a success.",
          "group": "authrep",
          "parameters": [
            {
              "name": "service_token",
              "dataType": "string",
              "required": true,
              "paramType": "query",
              "threescale_name": "service_tokens",
              "description": "Your service api key with 3scale (also known as service token)."
            },
            {
              "name": "service_id",
              "dataType": "string",
              "required": true,
              "paramType": "query",
              "threescale_name": "service_ids",
              "description": "Service id. Required."
            },
            {
              "name": "user_key",
              "dataType": "string",
              "required": true,
              "paramType": "query",
              "theescale_name": "user_keys",
              "description": "User Key (identifier and shared secret of the application if the auth. pattern is Api Key)"
            },
            {
              "name": "referrer",
              "dataType": "string",
              "required": false,
              "paramType": "query",
              "description": "Referrer IP Address or Domain. Required only if referrer filtering is enabled. If special value '*' (wildcard) is passed, the referrer check is bypassed."
            },
            {
              "name": "usage",
              "dataType": "hash",
              "required": false,
              "paramType": "query",
              "allowMultiple": false,
              "description": "Usage will increment the metrics with the values passed. The value can be only a positive integer (e.g. 1, 50). Reporting usage[hits]=1 will increment the hits counter by +1.",
              "parameters": [
                {
                  "name": "metric",
                  "dataType": "custom",
                  "required": false,
                  "paramType": "query",
                  "allowMultiple": true,
                  "threescale_name": "metric_names",
                  "description": "Metric to be reported"
                }
              ]
            },
            {
              "name": "log",
              "dataType": "hash",
              "required": false,
              "paramType": "query",
              "allowMultiple": false,
              "description": "Request Log allows to log status codes of your API back to 3scale to maintain a log of the latest activity on your API. Request Logs are optional and not available in all 3scale plans.",
              "parameters": [
                {
                  "name": "code",
                  "dataType": "string",
                  "paramType": "query",
                  "description_inline": true,
                  "description": "Response code of the response from your API (needs to be URL encoded). Optional. Truncated after 32bytes."
                }
              ]
            }
          ]
        }
      ]
    },
    {
      "path": "/transactions/oauth_authrep.xml",
      "format": "xml",
      "operations": [
        {
          "httpMethod": "GET",
          "nickname": "oauth_authrep",
          "deprecated": false,
          "summary": "AuthRep (OAuth authentication mode pattern)",
          "description": "<p>Authrep is a <b>'one-shot'</b> operation to authorize an application and report the associated transaction at the same time in the OAuth authentication pattern.<p>The main difference between this call and the regular authorize call is that usage will be reported if the authorization is successful. Authrep is the most convenient way to integrate your API with the 3scale's Service Manangement API since it does a 1:1 mapping between a request to your API and a request to 3scale's API.<p>If you do not want to do a request to 3scale for each request to your API or batch the reports you should use the Authorize and Report methods instead.<p>Authrep is <b>not a read-only</b> operation and will increment the values if the authorization step is a success.<p>When using this endpoint please pay attention at your handling of app_id and app_key parameters. If you don't specify an app_key, the endpoint assumes the app_id specified has already been authenticated by other means. If you specify the app_key parameter, even if it is empty, it will be checked against the application's keys. If you don't trust the app_id value you have, use app keys and specify one.<p>This call returns extra data (secret and redirect_url) needed to power OAuth APIs. It's only available for users with OAuth enabled APIs.",
          "group": "authrep",
          "parameters": [
            {
              "name": "service_token",
              "dataType": "string",
              "required": true,
              "paramType": "query",
              "threescale_name": "service_tokens",
              "description": "Your service api key with 3scale (also known as service token)."
            },
            {
              "name": "service_id",
              "dataType": "string",
              "required": true,
              "paramType": "query",
              "threescale_name": "service_ids",
              "description": "Service id. Required."
            },
            {
              "name": "app_id",
              "dataType": "string",
              "required": false,
              "paramType": "query",
              "threescale_name": "app_ids",
              "description": "Client Id (identifier of the application if the auth. pattern is OAuth, note that client_id == app_id)"
            },
            {
              "name": "app_key",
              "dataType": "string",
              "required": false,
              "paramType": "query",
              "threescale_name": "app_keys",
              "description": "App Key (shared secret of the application). The app key, if present, must match a key defined for the application. Note that empty values are considered invalid."
            },
            {
              "name": "referrer",
              "dataType": "string",
              "required": false,
              "paramType": "query",
              "description": "Referrer IP Address or Domain. Required only if referrer filtering is enabled. If special value '*' (wildcard) is passed, the referrer check is bypassed."
            },
            {
              "name": "usage",
              "dataType": "hash",
              "required": false,
              "paramType": "query",
              "allowMultiple": false,
              "description": "Usage will increment the metrics with the values passed. The value can be only a positive integer (e.g. 1, 50). Reporting usage[hits]=1 will increment the hits counter by +1.",
              "parameters": [
                {
                  "name": "metric",
                  "dataType": "custom",
                  "required": false,
                  "paramType": "query",
                  "allowMultiple": true,
                  "threescale_name": "metric_names",
                  "description": "Metric to be reported"
                }
              ]
            },
            {
              "name": "log",
              "dataType": "hash",
              "required": false,
              "paramType": "query",
              "allowMultiple": false,
              "description": "Request Log allows to log status codes of your API back to 3scale to maintain a log of the latest activity on your API. Request Logs are optional and not available in all 3scale plans.",
              "parameters": [
                {
                  "name": "code",
                  "dataType": "string",
                  "paramType": "query",
                  "description_inline": true,
                  "description": "Response code of the response from your API (needs to be URL encoded). Optional. Truncated after 32bytes."
                }
              ]
            },
            {
              "name": "redirect_url",
              "dataType": "string",
              "required": false,
              "paramType": "query",
              "description": "Optional redirect URL for OAuth. Will be validated if sent."
            },
            {
              "name": "redirect_uri",
              "dataType": "string",
              "required": false,
              "paramType": "query",
              "description": "Optional redirect URI for OAuth. This is the same as 'redirect_url', but if used you should expect a matching 'redirect_uri' response field."
            }
          ]
        }
      ]
    },
    {
      "path": "/transactions.xml",
      "format": "xml",
      "operations": [
        {
          "httpMethod": "POST",
          "summary": "Report (App Id authentication pattern)",
          "description": "<p>Report the transactions to 3scale backend.<p>This operation updates the metrics passed in the usage parameter. You can send up to 1K transactions in a single POST request. Transactions are processed asynchronously by the 3scale's backend.<p>Transactions from a single batch are reported only if all of them are valid. If there is an error in processing of at least one of them, none is reported.<p>Note that a batch can only report transactions to the same service, <em>service_id</em> is at the same level that <em>service_token</em>. Multiple report calls will have to be issued to report transactions to different services.<p>Be aware that reporting metrics that are limited at the time of reporting will have no effect.<p>Supported <code class='http'>Content-Type</code> values for this POST call are: <code class='http'>application/x-www-form-urlencoded</code>.",
          "group": "report",
          "parameters": [
            {
              "name": "service_token",
              "dataType": "string",
              "required": true,
              "paramType": "query",
              "threescale_name": "service_tokens",
              "description": "Your service api key with 3scale (also known as service token)."
            },
            {
              "name": "service_id",
              "dataType": "string",
              "required": true,
              "paramType": "query",
              "threescale_name": "service_ids",
              "description": "Service id. Required."
            },
            {
              "name": "transactions",
              "dataType": "array",
              "required": true,
              "paramType": "query",
              "allowMultiple": true,
              "description": "Transactions to be reported. There is a limit of 1000 transactions to be reported on a single request.",
              "parameters": [
                {
                  "name": "app_id",
                  "dataType": "string",
                  "required": true,
                  "paramType": "query",
                  "threescale_name": "app_ids",
                  "description": "App Id (identifier of the application if the auth. pattern is App Id)",
                  "description_inline": true
                },
                {
                  "name": "timestamp",
                  "dataType": "string",
                  "required": false,
                  "paramType": "query",
                  "description": "If passed, it should be the time when the transaction took place. Format: Either a UNIX UTC timestamp (seconds from the UNIX Epoch), or YYYY-MM-DD HH:MM:SS for UTC, add -HH:MM or +HH:MM for time offset. For instance, 2011-12-30 22:15:31 -08:00.",
                  "description_inline": true
                },
                {
                  "name": "usage",
                  "dataType": "hash",
                  "required": false,
                  "paramType": "query",
                  "allowMultiple": false,
                  "description": "Usage will increment the metrics with the values passed. The value can be only a positive integer (e.g. 1, 50). Reporting usage[hits]=1 will increment the hits counter by +1.",
                  "parameters": [
                    {
                      "name": "metric",
                      "dataType": "custom",
                      "required": false,
                      "paramType": "query",
                      "allowMultiple": true,
                      "threescale_name": "metric_names",
                      "description": "Metric to be reported"
                    }
                  ]
                },
                {
                  "name": "log",
                  "dataType": "hash",
                  "required": false,
                  "paramType": "query",
                  "allowMultiple": false,
                  "description": "Request Log allows to log status codes of your API back to 3scale to maintain a log of the latest activity on your API. Request Logs are optional and not available in all 3scale plans.",
                  "parameters": [
                    {
                      "name": "code",
                      "dataType": "string",
                      "paramType": "query",
                      "description_inline": true,
                      "description": "Response code of the response from your API (needs to be URL encoded). Optional. Truncated after 32bytes."
                    }
                  ]
                }
              ]
            }
          ]
        }
      ]
    },
    {
      "path": "/transactions.xml",
      "format": "xml",
      "operations": [
        {
          "httpMethod": "POST",
          "summary": "Report (API Key authentication pattern)",
          "description": "<p>Report the transactions to 3scale backend.<p>This operation updates the metrics passed in the usage parameter. You can send up to 1K transactions in a single POST request. Transactions are processed asynchronously by the 3scale's backend.<p>Transactions from a single batch are reported only if all of them are valid. If there is an error in processing of at least one of them, none is reported.<p>Note that a batch can only report transactions to the same service, <em>service_id</em> is at the same level that <em>service_token</em>. Multiple report calls will have to be issued to report transactions to different services.<p>Be aware that reporting metrics that are limited at the time of reporting will have no effect.<p>Supported <code class='http'>Content-Type</code> values for this POST call are: <code class='http'>application/x-www-form-urlencoded</code>.",
          "group": "report",
          "parameters": [
            {
              "name": "service_token",
              "dataType": "string",
              "required": true,
              "paramType": "query",
              "threescale_name": "service_tokens",
              "description": "Your service api key with 3scale (also known as service token)."
            },
            {
              "name": "service_id",
              "dataType": "string",
              "required": true,
              "paramType": "query",
              "threescale_name": "service_ids",
              "description": "Service id. Required."
            },
            {
              "name": "transactions",
              "dataType": "array",
              "required": true,
              "paramType": "query",
              "allowMultiple": true,
              "description": "Transactions to be reported. There is a limit of 1000 transactions to be reported on a single request.",
              "parameters": [
                {
                  "name": "user_key",
                  "dataType": "string",
                  "required": true,
                  "paramType": "query",
                  "theescale_name": "user_keys",
                  "description": "User Key (identifier and shared secret of the application if the auth. pattern is Api Key)",
                  "description_inline": true
                },
                {
                  "name": "timestamp",
                  "dataType": "string",
                  "required": false,
                  "paramType": "query",
                  "description": "If passed, it should be the time when the transaction took place. Format: Either a UNIX UTC timestamp (seconds from the UNIX Epoch), or YYYY-MM-DD HH:MM:SS for UTC, add -HH:MM or +HH:MM for time offset. For instance, 2011-12-30 22:15:31 -08:00.",
                  "description_inline": true
                },
                {
                  "name": "usage",
                  "dataType": "hash",
                  "required": false,
                  "paramType": "query",
                  "allowMultiple": false,
                  "description": "Usage will increment the metrics with the values passed. The value can be only a positive integer (e.g. 1, 50). Reporting usage[hits]=1 will increment the hits counter by +1.",
                  "parameters": [
                    {
                      "name": "metric",
                      "dataType": "custom",
                      "required": false,
                      "paramType": "query",
                      "allowMultiple": true,
                      "threescale_name": "metric_names",
                      "description": "Metric to be reported"
                    }
                  ]
                },
                {
                  "name": "log",
                  "dataType": "hash",
                  "required": false,
                  "paramType": "query",
                  "allowMultiple": false,
                  "description": "Request Log allows to log status codes of your API back to 3scale to maintain a log of the latest activity on your API. Request Logs are optional and not available in all 3scale plans.",
                  "parameters": [
                    {
                      "name": "code",
                      "dataType": "string",
                      "paramType": "query",
                      "description_inline": true,
                      "description": "Response code of the response from your API (needs to be URL encoded). Optional. Truncated after 32bytes."
                    }
                  ]
                }
              ]
            }
          ]
        }
      ]
    },
    {
      "path": "/transactions.xml",
      "format": "xml",
      "operations": [
        {
          "httpMethod": "POST",
          "summary": "Report (OAuth authentication pattern)",
          "description": "<p>Report the transactions to 3scale backend.<p>This operation updates the metrics passed in the usage parameter. You can send up to 1K transactions in a single POST request. Transactions are processed asynchronously by the 3scale's backend.<p>Transactions from a single batch are reported only if all of them are valid. If there is an error in processing of at least one of them, none is reported.<p>Note that a batch can only report transactions to the same service, <em>service_id</em> is at the same level that <em>service_token</em>. Multiple report calls will have to be issued to report transactions to different services.<p>Be aware that reporting metrics that are limited at the time of reporting will have no effect.<p>Supported <code class='http'>Content-Type</code> values for this POST call are: <code class='http'>application/x-www-form-urlencoded</code>.",
          "group": "report",
          "parameters": [
            {
              "name": "service_token",
              "dataType": "string",
              "required": true,
              "paramType": "query",
              "threescale_name": "service_tokens",
              "description": "Your service api key with 3scale (also known as service token)."
            },
            {
              "name": "service_id",
              "dataType": "string",
              "required": true,
              "paramType": "query",
              "threescale_name": "service_ids",
              "description": "Service id. Required."
            },
            {
              "name": "transactions",
              "dataType": "array",
              "required": true,
              "paramType": "query",
              "allowMultiple": true,
              "description": "Transactions to be reported. There is a limit of 1000 transactions to be reported on a single request.",
              "parameters": [
                {
                  "name": "app_id",
                  "dataType": "string",
                  "required": false,
                  "paramType": "query",
                  "threescale_name": "app_ids",
                  "description": "Client Id (identifier of the application if the auth. pattern is OAuth, note that client_id == app_id)",
                  "description_inline": true
                },
                {
                  "name": "timestamp",
                  "dataType": "string",
                  "required": false,
                  "paramType": "query",
                  "description": "If passed, it should be the time when the transaction took place. Format: Either a UNIX UTC timestamp (seconds from the UNIX Epoch), or YYYY-MM-DD HH:MM:SS for UTC, add -HH:MM or +HH:MM for time offset. For instance, 2011-12-30 22:15:31 -08:00.",
                  "description_inline": true
                },
                {
                  "name": "usage",
                  "dataType": "hash",
                  "required": false,
                  "paramType": "query",
                  "allowMultiple": false,
                  "description": "Usage will increment the metrics with the values passed. The value can be only a positive integer (e.g. 1, 50). Reporting usage[hits]=1 will increment the hits counter by +1.",
                  "parameters": [
                    {
                      "name": "metric",
                      "dataType": "custom",
                      "required": false,
                      "paramType": "query",
                      "allowMultiple": true,
                      "threescale_name": "metric_names",
                      "description": "Metric to be reported"
                    }
                  ]
                },
                {
                  "name": "log",
                  "dataType": "hash",
                  "required": false,
                  "paramType": "query",
                  "allowMultiple": false,
                  "description": "Request Log allows to log status codes of your API back to 3scale to maintain a log of the latest activity on your API. Request Logs are optional and not available in all 3scale plans.",
                  "parameters": [
                    {
                      "name": "code",
                      "dataType": "string",
                      "paramType": "query",
                      "description_inline": true,
                      "description": "Response code of the response from your API (needs to be URL encoded). Optional. Truncated after 32bytes."
                    }
                  ]
                }
              ]
            }
          ]
        }
      ]
    }
  ]
}