IssueTrackingApi
- List Tags
- Create Comment
- List Comments
- Delete Comment
- Get Comment
- Update Comment
- Create Ticket
- List Tickets
- Delete Ticket
- Get Ticket
- Update Ticket
- List Users
- Get User
- List Collections
- Get Collection
Method: collectionTagsAll
Apideck->getIssueTrackingApi()->collectionTagsAll($data)
Name | Type | Description | Notes |
---|---|---|---|
collection_id | string | The collection ID | |
x_apideck_consumer_id | string | ID of the consumer which you want to get or push data from | |
x_apideck_app_id | string | The ID of your Unify application | |
x_apideck_service_id | string | Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API. | |
cursor | string | Cursor to start from. You can find cursors for next/previous pages in the meta.cursors property of the response. | |
pass_through | \Apideck\Client\Model\PassThroughQuery | Optional unmapped key/values that will be passed through to downstream as query parameters. Ie: ?pass_through[search]=leads becomes ?search=leads | |
fields | string | The 'fields' parameter allows API users to specify the fields they want to include in the API response. If this parameter is not present, the API will return all available fields. If this parameter is present, only the fields specified in the comma-separated string will be included in the response. Nested properties can also be requested by using a dot notation. Example: `fields=name,email,addresses.city` In the example above, the response will only include the fields "name", "email" and "addresses.city". If any other fields are available, they will be excluded. |
|
raw | [bool] | Include raw response. Mostly used for debugging purposes | (optional) defaults to false |
limit | [int] | Number of results to return. Minimum 1, Maximum 200, Default 20 | (optional) defaults to 20 |
\Apideck\Client\Model\GetCollectionTagsResponse
Status code | Description |
---|---|
200 | List Tags |
400 | Bad Request |
401 | Unauthorized |
402 | Payment Required |
404 | The specified resource was not found |
422 | Unprocessable |
4/5xx | Unexpected error |
<?php
require('vendor/autoload.php');
use Apideck\Client\Apideck;
use Apideck\Client\ApideckConfiguration;
use Apideck\Client\ApiException;
$config = new ApideckConfiguration('<insert-api-key-here>', '<insert-application-id-here>', '<insert-consumer-id-here>', '<insert-service-id-here>');
$apideck = new Apideck($config);
try {
$response = $apideck->getIssueTrackingApi()->collectionTagsAll('collection_id_example');
var_dump('API called successfully', $response);
} catch(ApiException $error) {
var_dump('API called failed', $error);
}
[Back to top] [Back to API list] [Back to README]
Method: collectionTicketCommentsAdd
Apideck->getIssueTrackingApi()->collectionTicketCommentsAdd($data)
Name | Type | Description | Notes |
---|---|---|---|
collection_id | string | The collection ID | |
ticket_id | string | ID of the ticket you are acting upon. | |
collection_ticket_comment | \Apideck\Client\Model\CollectionTicketComment | ||
x_apideck_consumer_id | string | ID of the consumer which you want to get or push data from | |
x_apideck_app_id | string | The ID of your Unify application | |
x_apideck_service_id | string | Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API. | |
raw | [bool] | Include raw response. Mostly used for debugging purposes | (optional) defaults to false |
\Apideck\Client\Model\CreateCommentResponse
Status code | Description |
---|---|
201 | Create a Comment |
400 | Bad Request |
401 | Unauthorized |
402 | Payment Required |
404 | The specified resource was not found |
422 | Unprocessable |
4/5xx | Unexpected error |
<?php
require('vendor/autoload.php');
use Apideck\Client\Apideck;
use Apideck\Client\ApideckConfiguration;
use Apideck\Client\ApiException;
$config = new ApideckConfiguration('<insert-api-key-here>', '<insert-application-id-here>', '<insert-consumer-id-here>', '<insert-service-id-here>');
$apideck = new Apideck($config);
try {
$response = $apideck->getIssueTrackingApi()->collectionTicketCommentsAdd('collection_id_example', 'ticket_id_example', $collectionTicketComment);
var_dump('API called successfully', $response);
} catch(ApiException $error) {
var_dump('API called failed', $error);
}
[Back to top] [Back to API list] [Back to README]
Method: collectionTicketCommentsAll
Apideck->getIssueTrackingApi()->collectionTicketCommentsAll($data)
Name | Type | Description | Notes |
---|---|---|---|
collection_id | string | The collection ID | |
ticket_id | string | ID of the ticket you are acting upon. | |
x_apideck_consumer_id | string | ID of the consumer which you want to get or push data from | |
x_apideck_app_id | string | The ID of your Unify application | |
x_apideck_service_id | string | Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API. | |
cursor | string | Cursor to start from. You can find cursors for next/previous pages in the meta.cursors property of the response. | |
sort | \Apideck\Client\Model\CommentsSort | Apply sorting | |
pass_through | \Apideck\Client\Model\PassThroughQuery | Optional unmapped key/values that will be passed through to downstream as query parameters. Ie: ?pass_through[search]=leads becomes ?search=leads | |
fields | string | The 'fields' parameter allows API users to specify the fields they want to include in the API response. If this parameter is not present, the API will return all available fields. If this parameter is present, only the fields specified in the comma-separated string will be included in the response. Nested properties can also be requested by using a dot notation. Example: `fields=name,email,addresses.city` In the example above, the response will only include the fields "name", "email" and "addresses.city". If any other fields are available, they will be excluded. |
|
raw | [bool] | Include raw response. Mostly used for debugging purposes | (optional) defaults to false |
limit | [int] | Number of results to return. Minimum 1, Maximum 200, Default 20 | (optional) defaults to 20 |
\Apideck\Client\Model\GetCommentsResponse
Status code | Description |
---|---|
200 | List Comments |
400 | Bad Request |
401 | Unauthorized |
402 | Payment Required |
404 | The specified resource was not found |
422 | Unprocessable |
4/5xx | Unexpected error |
<?php
require('vendor/autoload.php');
use Apideck\Client\Apideck;
use Apideck\Client\ApideckConfiguration;
use Apideck\Client\ApiException;
$config = new ApideckConfiguration('<insert-api-key-here>', '<insert-application-id-here>', '<insert-consumer-id-here>', '<insert-service-id-here>');
$apideck = new Apideck($config);
try {
$response = $apideck->getIssueTrackingApi()->collectionTicketCommentsAll('collection_id_example', 'ticket_id_example');
var_dump('API called successfully', $response);
} catch(ApiException $error) {
var_dump('API called failed', $error);
}
[Back to top] [Back to API list] [Back to README]
Method: collectionTicketCommentsDelete
Apideck->getIssueTrackingApi()->collectionTicketCommentsDelete($data)
Name | Type | Description | Notes |
---|---|---|---|
id | string | ID of the record you are acting upon. | |
collection_id | string | The collection ID | |
ticket_id | string | ID of the ticket you are acting upon. | |
x_apideck_consumer_id | string | ID of the consumer which you want to get or push data from | |
x_apideck_app_id | string | The ID of your Unify application | |
x_apideck_service_id | string | Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API. | |
raw | [bool] | Include raw response. Mostly used for debugging purposes | (optional) defaults to false |
\Apideck\Client\Model\DeleteCommentResponse
Status code | Description |
---|---|
200 | Delete a Comment |
400 | Bad Request |
401 | Unauthorized |
402 | Payment Required |
404 | The specified resource was not found |
422 | Unprocessable |
4/5xx | Unexpected error |
<?php
require('vendor/autoload.php');
use Apideck\Client\Apideck;
use Apideck\Client\ApideckConfiguration;
use Apideck\Client\ApiException;
$config = new ApideckConfiguration('<insert-api-key-here>', '<insert-application-id-here>', '<insert-consumer-id-here>', '<insert-service-id-here>');
$apideck = new Apideck($config);
try {
$response = $apideck->getIssueTrackingApi()->collectionTicketCommentsDelete('id_example', 'collection_id_example', 'ticket_id_example');
var_dump('API called successfully', $response);
} catch(ApiException $error) {
var_dump('API called failed', $error);
}
[Back to top] [Back to API list] [Back to README]
Method: collectionTicketCommentsOne
Apideck->getIssueTrackingApi()->collectionTicketCommentsOne($data)
Name | Type | Description | Notes |
---|---|---|---|
id | string | ID of the record you are acting upon. | |
collection_id | string | The collection ID | |
ticket_id | string | ID of the ticket you are acting upon. | |
x_apideck_consumer_id | string | ID of the consumer which you want to get or push data from | |
x_apideck_app_id | string | The ID of your Unify application | |
x_apideck_service_id | string | Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API. | |
cursor | string | Cursor to start from. You can find cursors for next/previous pages in the meta.cursors property of the response. | |
fields | string | The 'fields' parameter allows API users to specify the fields they want to include in the API response. If this parameter is not present, the API will return all available fields. If this parameter is present, only the fields specified in the comma-separated string will be included in the response. Nested properties can also be requested by using a dot notation. Example: `fields=name,email,addresses.city` In the example above, the response will only include the fields "name", "email" and "addresses.city". If any other fields are available, they will be excluded. |
|
raw | [bool] | Include raw response. Mostly used for debugging purposes | (optional) defaults to false |
limit | [int] | Number of results to return. Minimum 1, Maximum 200, Default 20 | (optional) defaults to 20 |
\Apideck\Client\Model\GetCommentResponse
Status code | Description |
---|---|
200 | Get a Comment |
400 | Bad Request |
401 | Unauthorized |
402 | Payment Required |
404 | The specified resource was not found |
422 | Unprocessable |
4/5xx | Unexpected error |
<?php
require('vendor/autoload.php');
use Apideck\Client\Apideck;
use Apideck\Client\ApideckConfiguration;
use Apideck\Client\ApiException;
$config = new ApideckConfiguration('<insert-api-key-here>', '<insert-application-id-here>', '<insert-consumer-id-here>', '<insert-service-id-here>');
$apideck = new Apideck($config);
try {
$response = $apideck->getIssueTrackingApi()->collectionTicketCommentsOne('id_example', 'collection_id_example', 'ticket_id_example');
var_dump('API called successfully', $response);
} catch(ApiException $error) {
var_dump('API called failed', $error);
}
[Back to top] [Back to API list] [Back to README]
Method: collectionTicketCommentsUpdate
Apideck->getIssueTrackingApi()->collectionTicketCommentsUpdate($data)
Name | Type | Description | Notes |
---|---|---|---|
id | string | ID of the record you are acting upon. | |
collection_id | string | The collection ID | |
ticket_id | string | ID of the ticket you are acting upon. | |
collection_ticket_comment | \Apideck\Client\Model\CollectionTicketComment | ||
x_apideck_consumer_id | string | ID of the consumer which you want to get or push data from | |
x_apideck_app_id | string | The ID of your Unify application | |
x_apideck_service_id | string | Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API. | |
raw | [bool] | Include raw response. Mostly used for debugging purposes | (optional) defaults to false |
\Apideck\Client\Model\UpdateCommentResponse
Status code | Description |
---|---|
200 | Update a Comment |
400 | Bad Request |
401 | Unauthorized |
402 | Payment Required |
404 | The specified resource was not found |
422 | Unprocessable |
4/5xx | Unexpected error |
<?php
require('vendor/autoload.php');
use Apideck\Client\Apideck;
use Apideck\Client\ApideckConfiguration;
use Apideck\Client\ApiException;
$config = new ApideckConfiguration('<insert-api-key-here>', '<insert-application-id-here>', '<insert-consumer-id-here>', '<insert-service-id-here>');
$apideck = new Apideck($config);
try {
$response = $apideck->getIssueTrackingApi()->collectionTicketCommentsUpdate('id_example', 'collection_id_example', 'ticket_id_example', $collectionTicketComment);
var_dump('API called successfully', $response);
} catch(ApiException $error) {
var_dump('API called failed', $error);
}
[Back to top] [Back to API list] [Back to README]
Method: collectionTicketsAdd
Apideck->getIssueTrackingApi()->collectionTicketsAdd($data)
Name | Type | Description | Notes |
---|---|---|---|
collection_id | string | The collection ID | |
ticket | \Apideck\Client\Model\Ticket | ||
x_apideck_consumer_id | string | ID of the consumer which you want to get or push data from | |
x_apideck_app_id | string | The ID of your Unify application | |
x_apideck_service_id | string | Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API. | |
raw | [bool] | Include raw response. Mostly used for debugging purposes | (optional) defaults to false |
\Apideck\Client\Model\CreateTicketResponse
Status code | Description |
---|---|
201 | Create a Ticket |
400 | Bad Request |
401 | Unauthorized |
402 | Payment Required |
404 | The specified resource was not found |
422 | Unprocessable |
4/5xx | Unexpected error |
<?php
require('vendor/autoload.php');
use Apideck\Client\Apideck;
use Apideck\Client\ApideckConfiguration;
use Apideck\Client\ApiException;
$config = new ApideckConfiguration('<insert-api-key-here>', '<insert-application-id-here>', '<insert-consumer-id-here>', '<insert-service-id-here>');
$apideck = new Apideck($config);
try {
$response = $apideck->getIssueTrackingApi()->collectionTicketsAdd('collection_id_example', $collectionTicket);
var_dump('API called successfully', $response);
} catch(ApiException $error) {
var_dump('API called failed', $error);
}
[Back to top] [Back to API list] [Back to README]
Method: collectionTicketsAll
Apideck->getIssueTrackingApi()->collectionTicketsAll($data)
Name | Type | Description | Notes |
---|---|---|---|
collection_id | string | The collection ID | |
x_apideck_consumer_id | string | ID of the consumer which you want to get or push data from | |
x_apideck_app_id | string | The ID of your Unify application | |
x_apideck_service_id | string | Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API. | |
cursor | string | Cursor to start from. You can find cursors for next/previous pages in the meta.cursors property of the response. | |
sort | \Apideck\Client\Model\TicketsSort | Apply sorting | |
filter | \Apideck\Client\Model\IssuesFilter | Apply filters | |
pass_through | \Apideck\Client\Model\PassThroughQuery | Optional unmapped key/values that will be passed through to downstream as query parameters. Ie: ?pass_through[search]=leads becomes ?search=leads | |
fields | string | The 'fields' parameter allows API users to specify the fields they want to include in the API response. If this parameter is not present, the API will return all available fields. If this parameter is present, only the fields specified in the comma-separated string will be included in the response. Nested properties can also be requested by using a dot notation. Example: `fields=name,email,addresses.city` In the example above, the response will only include the fields "name", "email" and "addresses.city". If any other fields are available, they will be excluded. |
|
raw | [bool] | Include raw response. Mostly used for debugging purposes | (optional) defaults to false |
limit | [int] | Number of results to return. Minimum 1, Maximum 200, Default 20 | (optional) defaults to 20 |
\Apideck\Client\Model\GetTicketsResponse
Status code | Description |
---|---|
200 | List Tickets |
400 | Bad Request |
401 | Unauthorized |
402 | Payment Required |
404 | The specified resource was not found |
422 | Unprocessable |
4/5xx | Unexpected error |
<?php
require('vendor/autoload.php');
use Apideck\Client\Apideck;
use Apideck\Client\ApideckConfiguration;
use Apideck\Client\ApiException;
$config = new ApideckConfiguration('<insert-api-key-here>', '<insert-application-id-here>', '<insert-consumer-id-here>', '<insert-service-id-here>');
$apideck = new Apideck($config);
try {
$response = $apideck->getIssueTrackingApi()->collectionTicketsAll('collection_id_example');
var_dump('API called successfully', $response);
} catch(ApiException $error) {
var_dump('API called failed', $error);
}
[Back to top] [Back to API list] [Back to README]
Method: collectionTicketsDelete
Apideck->getIssueTrackingApi()->collectionTicketsDelete($data)
Name | Type | Description | Notes |
---|---|---|---|
ticket_id | string | ID of the ticket you are acting upon. | |
collection_id | string | The collection ID | |
x_apideck_consumer_id | string | ID of the consumer which you want to get or push data from | |
x_apideck_app_id | string | The ID of your Unify application | |
x_apideck_service_id | string | Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API. | |
raw | [bool] | Include raw response. Mostly used for debugging purposes | (optional) defaults to false |
\Apideck\Client\Model\DeleteTicketResponse
Status code | Description |
---|---|
200 | Delete a Ticket |
400 | Bad Request |
401 | Unauthorized |
402 | Payment Required |
404 | The specified resource was not found |
422 | Unprocessable |
4/5xx | Unexpected error |
<?php
require('vendor/autoload.php');
use Apideck\Client\Apideck;
use Apideck\Client\ApideckConfiguration;
use Apideck\Client\ApiException;
$config = new ApideckConfiguration('<insert-api-key-here>', '<insert-application-id-here>', '<insert-consumer-id-here>', '<insert-service-id-here>');
$apideck = new Apideck($config);
try {
$response = $apideck->getIssueTrackingApi()->collectionTicketsDelete('ticket_id_example', 'collection_id_example');
var_dump('API called successfully', $response);
} catch(ApiException $error) {
var_dump('API called failed', $error);
}
[Back to top] [Back to API list] [Back to README]
Method: collectionTicketsOne
Apideck->getIssueTrackingApi()->collectionTicketsOne($data)
Name | Type | Description | Notes |
---|---|---|---|
ticket_id | string | ID of the ticket you are acting upon. | |
collection_id | string | The collection ID | |
x_apideck_consumer_id | string | ID of the consumer which you want to get or push data from | |
x_apideck_app_id | string | The ID of your Unify application | |
x_apideck_service_id | string | Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API. | |
fields | string | The 'fields' parameter allows API users to specify the fields they want to include in the API response. If this parameter is not present, the API will return all available fields. If this parameter is present, only the fields specified in the comma-separated string will be included in the response. Nested properties can also be requested by using a dot notation. Example: `fields=name,email,addresses.city` In the example above, the response will only include the fields "name", "email" and "addresses.city". If any other fields are available, they will be excluded. |
|
raw | [bool] | Include raw response. Mostly used for debugging purposes | (optional) defaults to false |
\Apideck\Client\Model\GetTicketResponse
Status code | Description |
---|---|
200 | Get a Ticket |
400 | Bad Request |
401 | Unauthorized |
402 | Payment Required |
404 | The specified resource was not found |
422 | Unprocessable |
4/5xx | Unexpected error |
<?php
require('vendor/autoload.php');
use Apideck\Client\Apideck;
use Apideck\Client\ApideckConfiguration;
use Apideck\Client\ApiException;
$config = new ApideckConfiguration('<insert-api-key-here>', '<insert-application-id-here>', '<insert-consumer-id-here>', '<insert-service-id-here>');
$apideck = new Apideck($config);
try {
$response = $apideck->getIssueTrackingApi()->collectionTicketsOne('ticket_id_example', 'collection_id_example');
var_dump('API called successfully', $response);
} catch(ApiException $error) {
var_dump('API called failed', $error);
}
[Back to top] [Back to API list] [Back to README]
Method: collectionTicketsUpdate
Apideck->getIssueTrackingApi()->collectionTicketsUpdate($data)
Name | Type | Description | Notes |
---|---|---|---|
ticket_id | string | ID of the ticket you are acting upon. | |
collection_id | string | The collection ID | |
ticket | \Apideck\Client\Model\Ticket | ||
x_apideck_consumer_id | string | ID of the consumer which you want to get or push data from | |
x_apideck_app_id | string | The ID of your Unify application | |
x_apideck_service_id | string | Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API. | |
raw | [bool] | Include raw response. Mostly used for debugging purposes | (optional) defaults to false |
\Apideck\Client\Model\UpdateTicketResponse
Status code | Description |
---|---|
200 | Update a Ticket |
400 | Bad Request |
401 | Unauthorized |
402 | Payment Required |
404 | The specified resource was not found |
422 | Unprocessable |
4/5xx | Unexpected error |
<?php
require('vendor/autoload.php');
use Apideck\Client\Apideck;
use Apideck\Client\ApideckConfiguration;
use Apideck\Client\ApiException;
$config = new ApideckConfiguration('<insert-api-key-here>', '<insert-application-id-here>', '<insert-consumer-id-here>', '<insert-service-id-here>');
$apideck = new Apideck($config);
try {
$response = $apideck->getIssueTrackingApi()->collectionTicketsUpdate('ticket_id_example', 'collection_id_example', $collectionTicket);
var_dump('API called successfully', $response);
} catch(ApiException $error) {
var_dump('API called failed', $error);
}
[Back to top] [Back to API list] [Back to README]
Method: collectionUsersAll
Apideck->getIssueTrackingApi()->collectionUsersAll($data)
Name | Type | Description | Notes |
---|---|---|---|
collection_id | string | The collection ID | |
x_apideck_consumer_id | string | ID of the consumer which you want to get or push data from | |
x_apideck_app_id | string | The ID of your Unify application | |
x_apideck_service_id | string | Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API. | |
cursor | string | Cursor to start from. You can find cursors for next/previous pages in the meta.cursors property of the response. | |
pass_through | \Apideck\Client\Model\PassThroughQuery | Optional unmapped key/values that will be passed through to downstream as query parameters. Ie: ?pass_through[search]=leads becomes ?search=leads | |
fields | string | The 'fields' parameter allows API users to specify the fields they want to include in the API response. If this parameter is not present, the API will return all available fields. If this parameter is present, only the fields specified in the comma-separated string will be included in the response. Nested properties can also be requested by using a dot notation. Example: `fields=name,email,addresses.city` In the example above, the response will only include the fields "name", "email" and "addresses.city". If any other fields are available, they will be excluded. |
|
raw | [bool] | Include raw response. Mostly used for debugging purposes | (optional) defaults to false |
limit | [int] | Number of results to return. Minimum 1, Maximum 200, Default 20 | (optional) defaults to 20 |
\Apideck\Client\Model\GetCollectionUsersResponse
Status code | Description |
---|---|
200 | Users |
400 | Bad Request |
401 | Unauthorized |
402 | Payment Required |
404 | The specified resource was not found |
422 | Unprocessable |
4/5xx | Unexpected error |
<?php
require('vendor/autoload.php');
use Apideck\Client\Apideck;
use Apideck\Client\ApideckConfiguration;
use Apideck\Client\ApiException;
$config = new ApideckConfiguration('<insert-api-key-here>', '<insert-application-id-here>', '<insert-consumer-id-here>', '<insert-service-id-here>');
$apideck = new Apideck($config);
try {
$response = $apideck->getIssueTrackingApi()->collectionUsersAll('collection_id_example');
var_dump('API called successfully', $response);
} catch(ApiException $error) {
var_dump('API called failed', $error);
}
[Back to top] [Back to API list] [Back to README]
Method: collectionUsersOne
Apideck->getIssueTrackingApi()->collectionUsersOne($data)
Name | Type | Description | Notes |
---|---|---|---|
collection_id | string | The collection ID | |
id | string | ID of the record you are acting upon. | |
x_apideck_consumer_id | string | ID of the consumer which you want to get or push data from | |
x_apideck_app_id | string | The ID of your Unify application | |
x_apideck_service_id | string | Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API. | |
fields | string | The 'fields' parameter allows API users to specify the fields they want to include in the API response. If this parameter is not present, the API will return all available fields. If this parameter is present, only the fields specified in the comma-separated string will be included in the response. Nested properties can also be requested by using a dot notation. Example: `fields=name,email,addresses.city` In the example above, the response will only include the fields "name", "email" and "addresses.city". If any other fields are available, they will be excluded. |
|
raw | [bool] | Include raw response. Mostly used for debugging purposes | (optional) defaults to false |
\Apideck\Client\Model\GetCollectionUserResponse
Status code | Description |
---|---|
200 | User |
400 | Bad Request |
401 | Unauthorized |
402 | Payment Required |
404 | The specified resource was not found |
422 | Unprocessable |
4/5xx | Unexpected error |
<?php
require('vendor/autoload.php');
use Apideck\Client\Apideck;
use Apideck\Client\ApideckConfiguration;
use Apideck\Client\ApiException;
$config = new ApideckConfiguration('<insert-api-key-here>', '<insert-application-id-here>', '<insert-consumer-id-here>', '<insert-service-id-here>');
$apideck = new Apideck($config);
try {
$response = $apideck->getIssueTrackingApi()->collectionUsersOne('collection_id_example', 'id_example');
var_dump('API called successfully', $response);
} catch(ApiException $error) {
var_dump('API called failed', $error);
}
[Back to top] [Back to API list] [Back to README]
Method: collectionsAll
Apideck->getIssueTrackingApi()->collectionsAll($data)
Name | Type | Description | Notes |
---|---|---|---|
x_apideck_consumer_id | string | ID of the consumer which you want to get or push data from | |
x_apideck_app_id | string | The ID of your Unify application | |
x_apideck_service_id | string | Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API. | |
cursor | string | Cursor to start from. You can find cursors for next/previous pages in the meta.cursors property of the response. | |
sort | \Apideck\Client\Model\CollectionsSort | Apply sorting | |
pass_through | \Apideck\Client\Model\PassThroughQuery | Optional unmapped key/values that will be passed through to downstream as query parameters. Ie: ?pass_through[search]=leads becomes ?search=leads | |
fields | string | The 'fields' parameter allows API users to specify the fields they want to include in the API response. If this parameter is not present, the API will return all available fields. If this parameter is present, only the fields specified in the comma-separated string will be included in the response. Nested properties can also be requested by using a dot notation. Example: `fields=name,email,addresses.city` In the example above, the response will only include the fields "name", "email" and "addresses.city". If any other fields are available, they will be excluded. |
|
raw | [bool] | Include raw response. Mostly used for debugging purposes | (optional) defaults to false |
limit | [int] | Number of results to return. Minimum 1, Maximum 200, Default 20 | (optional) defaults to 20 |
\Apideck\Client\Model\GetCollectionsResponse
Status code | Description |
---|---|
200 | List Collections |
400 | Bad Request |
401 | Unauthorized |
402 | Payment Required |
404 | The specified resource was not found |
422 | Unprocessable |
4/5xx | Unexpected error |
<?php
require('vendor/autoload.php');
use Apideck\Client\Apideck;
use Apideck\Client\ApideckConfiguration;
use Apideck\Client\ApiException;
$config = new ApideckConfiguration('<insert-api-key-here>', '<insert-application-id-here>', '<insert-consumer-id-here>', '<insert-service-id-here>');
$apideck = new Apideck($config);
try {
$response = $apideck->getIssueTrackingApi()->collectionsAll();
var_dump('API called successfully', $response);
} catch(ApiException $error) {
var_dump('API called failed', $error);
}
[Back to top] [Back to API list] [Back to README]
Method: collectionsOne
Apideck->getIssueTrackingApi()->collectionsOne($data)
Name | Type | Description | Notes |
---|---|---|---|
collection_id | string | The collection ID | |
x_apideck_consumer_id | string | ID of the consumer which you want to get or push data from | |
x_apideck_app_id | string | The ID of your Unify application | |
x_apideck_service_id | string | Provide the service id you want to call (e.g., pipedrive). Only needed when a consumer has activated multiple integrations for a Unified API. | |
fields | string | The 'fields' parameter allows API users to specify the fields they want to include in the API response. If this parameter is not present, the API will return all available fields. If this parameter is present, only the fields specified in the comma-separated string will be included in the response. Nested properties can also be requested by using a dot notation. Example: `fields=name,email,addresses.city` In the example above, the response will only include the fields "name", "email" and "addresses.city". If any other fields are available, they will be excluded. |
|
raw | [bool] | Include raw response. Mostly used for debugging purposes | (optional) defaults to false |
\Apideck\Client\Model\GetCollectionResponse
Status code | Description |
---|---|
200 | Get a Collection |
400 | Bad Request |
401 | Unauthorized |
402 | Payment Required |
404 | The specified resource was not found |
422 | Unprocessable |
4/5xx | Unexpected error |
<?php
require('vendor/autoload.php');
use Apideck\Client\Apideck;
use Apideck\Client\ApideckConfiguration;
use Apideck\Client\ApiException;
$config = new ApideckConfiguration('<insert-api-key-here>', '<insert-application-id-here>', '<insert-consumer-id-here>', '<insert-service-id-here>');
$apideck = new Apideck($config);
try {
$response = $apideck->getIssueTrackingApi()->collectionsOne('collection_id_example');
var_dump('API called successfully', $response);
} catch(ApiException $error) {
var_dump('API called failed', $error);
}