Mock sample for your project: Apacta API
Integrate with "Apacta API" from apacta.com in no time with Mockoon's ready to use mock sample
Apacta
apacta.com
Version: 0.0.1
Speed up your application development by using "Apacta API" ready-to-use mock sample. Mocking this API will allow you to start working in no time. No more accounts to create, API keys to provision, accesses to configure, unplanned downtime, just work.
It also improves your integration tests' quality and reliability by accounting for random failures, slow response time, etc.
Description
API for a tool to craftsmen used to register working hours, material usage and quality assurance.
Endpoint
The endpoint https://app.apacta.com/api/v1 should be used to communicate with the API. API access is only allowed with SSL encrypted connection (https).
Authentication
URL query authentication with an API key is used, so appending ?apikey={apikey} to the URL where {api_key} is found within Apacta settings is used for authentication
Pagination
If the endpoint returns a pagination object it means the endpoint supports pagination - currently it's only possible to change pages with ?page={page_number} but implementing custom page sizes are on the road map.
Search/filter
Is experimental but implemented in some cases - see the individual endpoints' docs for further explanation.
Ordering
Is currently experimental, but on some endpoints it's implemented on URL querys so eg. to order Invoices by invoicenumber appending ?sort=Invoices.invoicenumber&direction=desc would sort the list descending by the value of invoice_number.
Associations
Is currently implemented on an experimental basis where you can append eg. ?include=Contacts,Projects to the /api/v1/invoices/ endpoint to embed Contact and Project objects directly.
Project Files
Currently project files can be retrieved from two endpoints. /projects/{projectid}/files handles files uploaded from wall posts or forms. /projects/{projectid}/project_files allows uploading and showing files, not belonging to specific form or wall post.
Errors/Exceptions
422 (Validation)
Write something about how the errors object contains keys with the properties that failes validation like:
Other APIs in the same category
Apacta
Endpoint
The endpoint https://app.apacta.com/api/v1 should be used to communicate with the API. API access is only allowed with SSL encrypted connection (https).
Authentication
URL query authentication with an API key is used, so appending ?apikey={apikey} to the URL where {api_key} is found within Apacta settings is used for authentication
Pagination
If the endpoint returns a pagination object it means the endpoint supports pagination - currently it's only possible to change pages with ?page={page_number} but implementing custom page sizes are on the road map.
Search/filter
Is experimental but implemented in some cases - see the individual endpoints' docs for further explanation.
Ordering
Is currently experimental, but on some endpoints it's implemented on URL querys so eg. to order Invoices by invoicenumber appending ?sort=Invoices.invoicenumber&direction=desc would sort the list descending by the value of invoice_number.
Associations
Is currently implemented on an experimental basis where you can append eg. ?include=Contacts,Projects to the /api/v1/invoices/ endpoint to embed Contact and Project objects directly.
Project Files
Currently project files can be retrieved from two endpoints. /projects/{projectid}/files handles files uploaded from wall posts or forms. /projects/{projectid}/project_files allows uploading and showing files, not belonging to specific form or wall post.
Errors/Exceptions
422 (Validation)
Write something about how the errors object contains keys with the properties that failes validation like: