GET /v1/pdf/documentparser/templates/:id
Use the PDF.co dashbaord to manage your Document Parser Templates.
Please refer to the Document Parser Template Editor and PDF.co Document Parser: Template Creation Guide for more information.
Query parameters
No query parameters accepted.Responses
| Parameter | Type | Description |
|---|---|---|
id | integer | Unique identifier for the template |
type | string | Source of the template. The available sources are: user, system. |
title | string | Title of the template |
description | string | Description of what the template does |
created_at | String (ISO 8601) | Timestamp indicating when the template was initially created |
updated_at | String (ISO 8601) | Timestamp indicating the last time the template was modified |
body | string | Template content |
credits | integer | Number of credits consumed by the request |
remainingCredits | integer | Number of credits remaining in the account |
Inconsistent URL Encoding in cURL Output: When using cURL to make API requests, the output JSON may show URL characters encoded as Unicode escape sequences. For example, the ampersand character (
&) may appear as \u0026 in the cURL output. This is normal JSON encoding behavior and does not affect the validity of the URL. The URL will function correctly when used, as JSON parsers automatically decode these escape sequences. If you’re parsing the response programmatically, your JSON parser will handle this conversion automatically.Code Samples
- CURL
- JavaScript/Node.js
- Python
- C#
- Java
- PHP