-
Notifications
You must be signed in to change notification settings - Fork 2
Expand file tree
/
Copy pathtdocxcollection.yml
More file actions
3609 lines (3379 loc) · 109 KB
/
Copy pathtdocxcollection.yml
File metadata and controls
3609 lines (3379 loc) · 109 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
openapi: 3.0.0
info:
title: TurboDocx API Documentation
description: >-
Welcome to the TurboDocx API Documentation. This comprehensive guide is
designed to provide developers with all the information required to interact
with the TurboDocx platform programmatically.
Whether you're looking to automate document creation, manage your templates,
or integrate TurboDocx features into your application, you'll find the
necessary endpoints, parameters, and examples here.
## **Getting started guide**
Before diving into the specifics of the API, ensure that you have obtained
the necessary Access Token and have the correct permissions to access the
desired resources.
Keep your Access Token secure and do not expose them in publicly accessible
areas such as GitHub, client-side code, etc. **The Authentication and
Organization ID is a variable set at the root of the collection.**
## Base URL
All API requests should be made to the base URL provided upon your API key
registration. Typically, it looks like this:
``` typescript
https://api.turbodocx.com
```
## Authentication
TurboDocx is working on it's API Key flows, and for the time being, we
recommend grabbing the access token used from your user's accounts to
leverage our APIs. You can find an example on how to get your access token
in the `Blueprint` folder.
To use the Access Token, use the following under the `Authorization Header`
``` typescript
Authorization: Bearer YOUR_ACCESS_TOKEN
```
### Authentication error response
If an Access Token is missing, malformed, or invalid, you will receive an
HTTP 401 Unauthorized response code.
### **Need some help?**
In case you have questions, go through our tutorials ((link to your video or
help documentation here)). Or visit our FAQ page ((link to the relevant
page)).
Or you can check out our community forum, there’s a good chance our
community has an answer for you. Visit our developer forum ((link to
developer forum)) to review topics, ask questions, and learn from others.
`You can also document or add links to libraries, code examples, and other
resources needed to make a request.`
version: 1.0.0
servers:
- url: https://api.turbodocx.com
- url: https://app.turbodocx.com
tags:
- name: Blueprint
description: >-
# 🚀 Get started here
This guide walks you through the operational flows of TurboDocx.TurboDocx
is a Document and Slide Deck Generation Platform with an emphasis on
reusable content and flexible integrations to fit any use case. Below is
our API Documentation that will align with our corresponding UI.
## 🔖 **How to use this Flow**
### **Step 1: Get Access Token and Organization ID**
1. Log into TurboDocx via the UI (a proper API Key is in the works)
<img
src="https://lh7-us.googleusercontent.com/TXirIt7wFftqr41PsMPeIQs3Mp0ewHjUy2vjelOYNz1SOc_vWn5NXkbT1JXCD4NtPa6QCzZ2HdsTxY7erPr0TK11Pm-34ne5jgEpX3r9ZzBKmEHTtgK_wq3Vr9UUTDGIOhiZLx8F7sDx7JEn2449JQk">
2\. After logging in, open your browser developer tools.
<img
src="https://lh7-us.googleusercontent.com/EPoXUqoOjMAekM69H4SDCvhydTVsCftiO1tnPCEr5A91qxEEc1FxPhRrI5kCngoBy0iSvKXSKobnOhtaKgqLQRU3rqLXAfOfdWzlQ-fanhEVjzM0lpv-RmktClU45trDhLVo-rcX5iX6H1J275lYBPQ">
3\. Navigate to the network tab
<img
src="https://lh7-us.googleusercontent.com/KiyvSzik4vjpnwV5Ehbe44h_R94xkYWZbAS0cRiKvNmJpyYKCPn9EF98OTnf6u0Sv_nFUocfkU15BIPC0Oe0MukYBmxncQvrUpq_5czpbjv0Vji-KO9vcLr6M5Q__zwvtg_SSxPYBsRozfRpoit5jXE">
4\. Click on anything and observe the network trace and get the token from
the Authorization Header. This is a JWT and is the string after
`Bearer`(In the screenshot, we blurred out part of the token for security
purposes.)
<img
src="https://lh7-us.googleusercontent.com/eToIOYqhLY9AD1Ky9qHmtA7nI-iWjeJYI5gF5YTdjbok9g7PZz7DsqL3Q0MVtspoAXMQuVqPqCRxkUb-6LwYwgXfRUwQDHCDrPCqeNZTXeQ4mtcIx_7wjJAQy2XQPbPnQpxUHryNxRBh9CMkGSzMxjs">
5\. Capture your Organization ID noted under `x-Rapiddocx-Org-id`
<img
src="https://lh7-us.googleusercontent.com/Ux4wo1L4QPttxKN6Dqu0mYhxNA4PRarniADy1TaLHB_mBkehOFW5koncfvbkCpsgL1-FXf442v0VMo2BXbcNZvt34omHGskGkyPpl309uqtkJQXCP9RHrOCtdHVwJ761cfSGlvfqJSpKgHWCt165aGk">
6\. Set these variables in your Postman Collection
<img
src="https://content.pstmn.io/834125c9-927e-4cae-af77-f752fd0a2f84/aW1hZ2UucG5n"
width="1477" height="303">
### **Step 2: (Optional) Create Knowledgebase Entires**
<img
src="https://content.pstmn.io/83538b8c-35cb-426c-953a-2e92794b9d80/aW1hZ2UucG5n"
width="616" height="339">
The Knowledgebase is the central repository for reusable content within
TurboDocx. Knowledgebase content can be text, images, or HTML types.
The TurboDocx Engine automatically converts the formats in the final
document deliverable. TurboDocx also supports "Folder Variables" which are
knowledgebases specific to folders.
These will be merged into Deliverables in a later step.
### **Step 3: Create a New Template**
We typically recommend doing this in the UI, however, you can
programatically upload templates into TurboDocx. For this example, [please
use our SOW Template
provided](https://docs.google.com/document/d/1eGVfPnr0tGR9ofVKria21Ep5Rw4dKHe-/edit?usp=sharing&ouid=101706568972642413390&rtpof=true&sd=true).
1\. Preflight - Upload your Template and extract the Placeholders and
(optionally) use the preview. The most important item is knowing which
placeholders support "Rich Text Injection." (i.e. HTML and Image content).
Without knowing this, you will see the final result render with issues.
2\. Create your template, and (optionally) set Template Default Values.
Notate the TemplateID from the response.
<img
src="https://content.pstmn.io/8918dfec-df63-472b-890f-0ad7427d9109/VGVtcGxhdGVDcmVhdGlvbi5wbmc="
alt="Notate%20the%20Template%20ID%20in%20the%20response%20to%20be%20used%20in%20Step%204"
width="1179" height="469">
### **Step 4: Create the Deliverable**
Deliverables are the outputs from TurboDocx from merging the Variables and
other content.
1. (Optional) Using the TemplateID from the previous step, Get the
Template by ID. TurboDocx will _automatically merge_ centralized items
from the Knowledgebase and Folders with the template
2. Using the Variables from the template, fill in the remaining blanks and
merge them into the Deliverable
3. Capture the DeliverableID to be used in the next step
### **Step 5: Download the Deliverable**
Once the Deliverable is generated, you can download the document or PDF to
be used elsewhere.
- name: Blueprint > Step 2 (Optional) - Create Knowledgebase Entries
description: >-
<img
src="https://content.pstmn.io/74c09457-388d-49cf-bab5-19b04d22b2c3/aW1hZ2UucG5n"
alt="The%20UI%20equivalent%20of%20creating%20a%20Variable" width="1295"
height="873">
1. Using the three provided POST parameters, you will create a
CompanyName, Company Logo, and then a fictional "scope" table to be used
as a default inheritied value when creating a Deliverable.
2. Note - in the scope we provide "Subvariables" that can be swapped out.
We use {Technology} which can be platforms like AWS, Azure, GCP, etc..
- name: Blueprint > Step 3 - Create a Template
description: >-
<img
src="https://content.pstmn.io/0e5bc131-3951-40fa-90bf-981c4ccfa8a8/aW1hZ2UucG5n"
alt="The%20UI%20Equivalent%20of%20Creating%20a%20Template" width="1285"
height="857">
1. The first step is to extract the Template Placeholders to determine
whch fields support Rich Text Injection
2. The second step is to upload the Template with the Optional Default
Values (mirroring the items extracted from step 1). Note - the variables
are Stringified using a function such as `JSON.stringify()` prior to
uploading it to the endpoint.
- name: Blueprint > Step 4 - Create a Deliverable
description: >-
<img
src="https://content.pstmn.io/3dcb2b67-960d-4077-87d3-659e1799d313/aW1hZ2UucG5n"
alt="Creating%20a%20Deliverable%20in%20the%20UI%20with%20pre-merging%20shown."
width="1292" height="958">
When creating a Deliverable, TurboDocx's UI will automatically inherit in
the following order:
1. Template Defaults
2. Folder Variables
3. Knowledgebase Variables
Using the APIs, we can perform the same flow. We will get the Template by
ID, see the "pre-merged values" and then pass those values into the Create
Deliverable API.
- name: Variable Routes
description: >-
The `Variable` Route in the TurboDocx API allows users to dynamically
insert content into their document templates, slide decks, and knowledge
bases. The content of these variables can be plain text, HTML, or image
files, enabling a versatile approach to document customization and
automation.
<img
src="https://content.pstmn.io/1e4f2893-8f78-4632-b1eb-892e73f7f9a0/aW1hZ2UucG5n"
width="1916" height="887">
## Usage
### Populating the Knowledgebase (or Folder)
The Knowledgebase is a central repository for content that can be reused
across multiple templates and documents. By utilizing the `Variable`
Route, users can:
- **Create Variables**: Add new variables to the knowledgebase that can be
used as placeholders within templates. These variables are associated with
specific tags, enabling organized and efficient retrieval.
- **Update Variables**: Modify the content of existing variables to
reflect changes in information or strategy, ensuring that documents remain
up to date without the need to edit individual templates.
- **Delete Variables**: Remove variables that are no longer relevant from
the knowledgebase, maintaining a clean and focused content library.
### Managing Folders
Folders in TurboDocx help organize variables and templates by project,
department, or any other categorization that suits the business workflow.
The `Variable` Route allows users to:
- **Sort Variables into Folders**: Assign variables to folders for
improved document management. This helps users navigate large volumes of
content and templates with ease.
- **Retrieve Folder Contents**: Access all variables within a particular
folder, making it simple to find the content needed for a specific
document or template.
### Supported Types
The `Variable` Route supports three types of content, providing
flexibility in how information is presented in documents:
- **Text**: For inserting plain text content, such as names, dates, or
addresses.
- **HTML**: For rich text formatting options, like bold, italics, or
custom fonts, and for embedding other HTML-supported content within
documents.
- **Image**: For adding graphical elements, such as company logos, user
avatars, or product images.
## API Endpoints
The following endpoints are associated with the `Variable` Route:
- `POST /variable`: Create a new variable.
- `GET /variable`: Retrieve a list of all variables.
- `GET /variable/{id}`: Retrieve details about a specific variable.
- `PUT /variable/{id}`: Update an existing variable.
- `DELETE /variable/{id}`: Delete a specific variable.
By using these endpoints, users can automate the integration of dynamic
content into their documents, enhancing productivity and ensuring
consistency across all generated materials.
## Attributes
- `id` (string, optional): A unique identifier for the variable,
automatically generated if not provided.
- `name` (string, required): The display name of the variable for
identification within the user interface.
- `description` (string, optional): A brief description of the variable's
purpose or content.
- `tags` (array, optional): An array of tags associated with the variable
for organizational purposes.
- `placeholder` (string, required): A unique placeholder text that is used
to insert the variable content into documents.
- `text` (string, required): The content of the variable, which can be
text, HTML, or a base64 encoded string for images.
- `mimeType` (string, required): The type of content that the variable
holds, which can be `text`, `html`, or `image`.
- `allowRichTextInjection` (boolean, optional): Used in other parts of the
API, this specifies if this variable can be used in Rich Text Injection.
For knowledgebase/folders, it is best practice to leave this set to true.
- `templateFolderId` (string, conditionally required): The identifier of
the template folder to which this variable belongs. This field is required
if isGlobal is set to false or omitted. It should not be provided if
isGlobal is true.
- `isGlobal` (boolean, conditionally required): A flag indicating whether
the variable is global (i.e., part of the Knowledgebase). If true, the
variable is available across all templates and templateFolderId should not
be provided. This field is required if templateFolderId is not provided.
- name: Tag Routes
description: >-
<img
src="https://content.pstmn.io/a9f12bd9-6699-4fa4-bdfa-d5819fcd58e1/aW1hZ2UucG5n"
alt="" height="682" width="1907">
The Tag API endpoints facilitate efficient organization within the
TurboDocx platform by allowing users to manage the tagging system. Tags
serve as flexible identifiers that can be attached to Variables,
Templates, and Deliverables. Through the API, tags can be created,
retrieved, updated, and deleted, enabling automated categorization and
enhanced searchability.
## Usage
### Organization and Retrieval
Tags are instrumental in categorizing and retrieving various entities
within TurboDocx. They enable users to:
- **Create Tag**: Define new tags that can be applied to Variables,
Templates, and Deliverables for quick identification and grouping.
- **Retrieve Tags**: Fetch a list of all existing tags for review or to
identify which tag needs to be applied or edited.
- **Update Tag**: Modify existing tags to better reflect the grouped items
or to correct previous tag names.
- **Delete Tags**: Remove outdated or unnecessary tags from the system to
maintain a clean tagging structure.
### Searching with Tags
With tags applied, users can perform filtered searches across the
platform, significantly reducing the time required to locate specific
documents or content.
## API Endpoints
The following endpoints are used for managing tags within the TurboDocx
API:
### Create a Tag
- **POST** `/tag`
- **Description**: Add a new tag to the system.
### Retrieve Tags
- **GET** `/tag`
- **Description**: List all tags available in the system.
### Update a Tag
- **PUT** `/tag/{{tagId}}`
- **Description**: Modify an existing tag's label.
- **URL Parameters**:
- `tagId`: The ID of the tag to be updated.
### Delete a Tag
- **DELETE** `/tag/bulk/action/`
- **Description**: Remove a tags from the system
- name: Template Routes
- name: Template-Item Routes
description: >-
<img
src="https://content.pstmn.io/6061d955-106b-43b4-ac87-09b5cc6f5211/aW1hZ2UucG5n"
alt="This%20route%20gets%20all%20the%20root-level%20templates%20and%20folders.%20"
width="1292" height="962">
Templates have type set to template
Folders have type set to folder
- name: Deliverable Routes
- name: Webhook Routes
description: >-
The Webhook Routes API provides full lifecycle management for
TurboDocx signature webhooks. Webhooks let your application receive
real-time HTTP notifications when signature events occur — for example
when a document is completed or voided.
The SDK exposes a single fixed-name webhook per org (`signature`) that
mirrors the **Signature Webhooks** settings page in the TurboDocx UI.
Users who need multi-webhook management may call the REST API directly.
All routes require an **administrator** TDX- API key. Non-admin keys
receive a `403 Forbidden` response.
## Endpoints
- **POST** `/api/webhooks` — Register a new signature webhook.
- **GET** `/api/webhooks/signature` — Retrieve the webhook with delivery stats.
- **PATCH** `/api/webhooks/signature` — Update URLs, events, or active state.
- **DELETE** `/api/webhooks/signature` — Remove the webhook.
- **POST** `/api/webhooks/signature/test` — Send a test delivery.
- **POST** `/api/webhooks/signature/notify` — Send a manual notification.
- **POST** `/api/webhooks/signature/regenerate` — Rotate the HMAC secret.
- **GET** `/api/webhooks/signature/deliveries` — List delivery history.
- **POST** `/api/webhooks/signature/replay` — Retry a specific delivery.
- **GET** `/api/webhooks/signature/stats` — Aggregate delivery statistics.
paths:
/Variable:
post:
tags:
- Variable Routes
summary: Create Image Variable (Folder)
description: Create a new image variable inside a folder in your TurboDocx workspace. Image variables store uploaded files that can be inserted into templates during document generation. Supports tags, placeholders, and default values.
requestBody:
content:
application/json:
schema:
type: object
properties:
name:
type: string
description: The name of the variable
description:
type: string
description: The description of the variable
tags:
type: array
items:
type: string
description: List of tags associated with the variable
placeholder:
type: string
description: >-
A unique placeholder text that is used to insert the
variable content into documents
text:
type: string
description: >-
The content of the variable, which can be text, HTML, or a
base64 encoded string for images
mimeType:
type: string
description: >-
The type of content that the variable holds, which can be
`text`, `html`, or `image`
allowRichTextInjection:
type: boolean
description: >-
Used in other parts of the API, this specifies if this
variable can be used in Rich Text Injection. For
knowledgebase/folders, it is best practice to leave this set
to true
required:
- name
- placeholder
- text
- mimeType
parameters:
- name: authorization
in: header
schema:
type: string
example: Bearer {{TurboDocx Access Token}}
- name: x-rapiddocx-org-id
in: header
schema:
type: string
example: "{{TurboDocx Organization ID}}"
- name: accept
in: header
schema:
type: string
example: application/json, text/plain, */*
- name: accept-language
in: header
schema:
type: string
example: en-US,en;q=0.9
- name: content-type
in: header
schema:
type: string
example: application/json
- name: dnt
in: header
schema:
type: integer
example: "1"
- name: origin
in: header
schema:
type: string
example: https://app.turbodocx.com
- name: referer
in: header
schema:
type: string
example: https://app.turbodocx.com/
- name: sec-ch-ua-mobile
in: header
schema:
type: string
example: "?0"
- name: sec-ch-ua-platform
in: header
schema:
type: string
example: '"Windows"'
- name: sec-fetch-dest
in: header
schema:
type: string
example: empty
- name: sec-fetch-mode
in: header
schema:
type: string
example: cors
- name: sec-fetch-site
in: header
schema:
type: string
example: same-site
responses:
"200":
description: Successful response
content:
application/json: {}
get:
tags:
- Variable Routes
summary: Read Variables (Folder)
description: Retrieve all variables within a specific folder. Returns variable names, placeholders, descriptions, tags, and default values. Use this to list available variables before creating a deliverable.
parameters:
- name: accept
in: header
schema:
type: string
example: application/json, text/plain, */*
- name: accept-language
in: header
schema:
type: string
example: en-US,en;q=0.9
- name: authorization
in: header
schema:
type: string
example: Bearer {{TurboDocx Access Token}}
- name: x-rapiddocx-org-id
in: header
schema:
type: string
example: "{{TurboDocx Organization ID}}"
- name: dnt
in: header
schema:
type: integer
example: "1"
- name: if-none-match
in: header
schema:
type: string
example: W/"44c3-unzppoXln1hKA8phCj0wMh6F2bs"
- name: origin
in: header
schema:
type: string
example: https://app.turbodocx.com
- name: referer
in: header
schema:
type: string
example: https://app.turbodocx.com/
- name: sec-ch-ua
in: header
schema:
type: string
example: '"Google Chrome";v="123", "Not:A-Brand";v="8", "Chromium";v="123"'
- name: sec-ch-ua-mobile
in: header
schema:
type: string
example: "?0"
- name: sec-ch-ua-platform
in: header
schema:
type: string
example: '"Windows"'
- name: sec-fetch-dest
in: header
schema:
type: string
example: empty
- name: sec-fetch-mode
in: header
schema:
type: string
example: cors
- name: sec-fetch-site
in: header
schema:
type: string
example: same-site
- name: limit
in: query
schema:
type: integer
example: "5"
- name: showTags
in: query
schema:
type: boolean
example: "true"
- name: templateFolderId
in: query
schema:
type: string
example: "{{templateFolderId}}"
responses:
"200":
description: Successful response
content:
application/json: {}
/template/file:
post:
tags:
- Template Routes
summary: Extract Template Placeholders and Generate Preview
description: Upload a DOCX or PPTX file to extract all variable placeholders and generate a PDF preview. Returns the list of detected variables and a preview URL. Use this before creating a template to validate your document.
requestBody:
content:
multipart/form-data:
schema:
type: object
properties:
file:
type: string
description: This is an example Template
format: binary
parameters:
- name: x-filename
in: header
schema:
type: string
example: SOW Template.docx
- name: x-rapiddocx-org-id
in: header
schema:
type: string
example: "{{TurboDocx Organization ID}}"
- name: authorization
in: header
schema:
type: string
example: Bearer {{TurboDocx Access Token}}
- name: accept
in: header
schema:
type: string
example: application/json, text/plain, */*
- name: accept-language
in: header
schema:
type: string
example: en-US,en;q=0.9
- name: dnt
in: header
schema:
type: integer
example: "1"
- name: origin
in: header
schema:
type: string
example: https://app.turbodocx.com
- name: referer
in: header
schema:
type: string
example: https://app.turbodocx.com/
- name: sec-ch-ua
in: header
schema:
type: string
example: '"Google Chrome";v="123", "Not:A-Brand";v="8", "Chromium";v="123"'
- name: sec-ch-ua-mobile
in: header
schema:
type: string
example: "?0"
- name: sec-ch-ua-platform
in: header
schema:
type: string
example: '"Windows"'
- name: sec-fetch-dest
in: header
schema:
type: string
example: empty
- name: sec-fetch-mode
in: header
schema:
type: string
example: cors
- name: sec-fetch-site
in: header
schema:
type: string
example: same-site
responses:
"200":
description: Successful response
content:
application/json: {}
/template:
post:
tags:
- Template Routes
summary: Upload Template with Optional Default Values
description: Upload a DOCX or PPTX template file to TurboDocx with optional default variable values. The template is parsed for placeholders, a PDF preview is generated, and the template becomes available for deliverable creation.
requestBody:
content:
multipart/form-data:
schema:
type: object
properties:
templateFile:
type: string
format: binary
name:
type: string
example: SOW Template
description:
type: string
variables:
type: string
example: >-
[{"placeholder":"CustomerName","name":"CustomerName","allowRichTextInjection":false,"order":0,"count":25},{"placeholder":"ProjectName","name":"ProjectName","allowRichTextInjection":false,"order":1,"count":2},{"placeholder":"Date","name":"Date","allowRichTextInjection":false,"order":2,"count":2},{"placeholder":"CustomerLogo","name":"CustomerLogo","allowRichTextInjection":true,"order":3,"count":1},{"placeholder":"VersionNumber","name":"VersionNumber","allowRichTextInjection":false,"order":4,"count":1},{"placeholder":"Scope","name":"Scope","allowRichTextInjection":true,"order":5,"count":1},{"placeholder":"BillRate","name":"BillRate","allowRichTextInjection":false,"order":6,"count":1}]
tags:
type: string
example: "[]"
parameters:
- name: authorization
in: header
schema:
type: string
example: Bearer {{TurboDocx Access Token}}
- name: x-rapiddocx-org-id
in: header
schema:
type: string
example: "{{TurboDocx Organization ID}}"
- name: accept
in: header
schema:
type: string
example: application/json, text/plain, */*
- name: accept-language
in: header
schema:
type: string
example: en-US,en;q=0.9
- name: dnt
in: header
schema:
type: integer
example: "1"
- name: origin
in: header
schema:
type: string
example: https://app.turbodocx.com
responses:
"200":
description: Successful response
content:
application/json: {}
/template/{TemplateID}:
get:
tags:
- Template Routes
summary: Get Template by ID
description: Retrieve a single template by its unique ID. Returns template metadata, variable definitions, preview URL, tags, and folder information.
parameters:
- name: authorization
in: header
schema:
type: string
example: Bearer {{TurboDocx Access Token}}
- name: x-rapiddocx-org-id
in: header
schema:
type: string
example: "{{TurboDocx Organization ID}}"
- name: accept
in: header
schema:
type: string
example: application/json, text/plain, */*
- name: accept-language
in: header
schema:
type: string
example: en-US,en;q=0.9
- name: dnt
in: header
schema:
type: integer
example: "1"
- name: if-none-match
in: header
schema:
type: string
example: W/"2534-f/UbhD2HIM3HP3jOlbqIO79TVrQ"
- name: origin
in: header
schema:
type: string
example: https://app.turbodocx.com
- name: referer
in: header
schema:
type: string
example: https://app.turbodocx.com/
- name: showTags
in: query
schema:
type: boolean
example: "true"
- name: TemplateID
in: path
schema:
type: string
required: true
responses:
"200":
description: Successful response
content:
application/json: {}
/deliverable:
post:
tags:
- Blueprint > Step 4 - Create a Deliverable
summary: Create Deliverable
description: Generate a document deliverable from a template by providing variable values. Combines template placeholders with supplied data to produce a finished DOCX, PPTX, or PDF document.
requestBody:
content:
application/json:
schema:
type: object
properties:
templateId:
type: string
example: TemplateID
name:
type: string
example: SOW for Waystar Royco
description:
type: string
example: hello
variables:
type: array
items:
type: object
properties:
mimeType:
type: string
example: text
name:
type: string
example: VersionNumber
placeholder:
type: string
example: VersionNumber
text:
type: string
example: "1.0"
allowRichTextInjection:
type: integer
example: 0
autogenerated:
type: boolean
example: true
count:
type: integer