forked from mvanhorn/printing-press-library
-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathspec.yaml
More file actions
1336 lines (1293 loc) · 63.7 KB
/
Copy pathspec.yaml
File metadata and controls
1336 lines (1293 loc) · 63.7 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:
description: |
Welcome to the Bento API v1 documentation. This API allows you to interact with Bento's powerful email marketing and customer engagement platform.
Base URL for API v1 calls: https://app.bentonow.com/api/v1/
API v1 is actively maintained and regularly updated to provide you with the best possible experience.
## Important Note
For the most up-to-date and comprehensive documentation, please visit our official documentation site at https://docs.bentonow.com/
title: Bento API v1
version: "1.0"
servers:
- url: "https://app.bentonow.com"
description: Production server
- url: "http://app.devbento.localhost/"
description: Development server
tags:
- name: subscribers
description: Manage your subscriber base, including creation, updates, and retrieval of subscriber information.
x-displayName: Subscribers
- name: events
description: Track and manage events associated with your subscribers.
x-displayName: Events
- name: emails
description: Create, send, and manage email campaigns.
x-displayName: Emails
- name: tags
description: Organize and categorize your subscribers with tags.
x-displayName: Tags
- name: fields
description: Define and manage custom fields for your subscribers.
x-displayName: Fields
- name: broadcasts
description: Create and manage email broadcasts to your subscriber base.
x-displayName: Broadcasts
- name: experimental
description: Access experimental APIs designed for specific use cases. Use with caution as these may change.
x-displayName: Experimental API
- name: stats
description: Retrieve statistical data about your account. IMPORTANT — Never use these endpoints in client-side code.
x-displayName: Stats
paths:
/api/v1/batch/subscribers:
post:
security:
- BasicAuth: []
tags:
- subscribers
summary: Import or Update Subscribers in Bulk
parameters:
- name: site_uuid
in: query
required: true
description: Your site's unique identifier.
schema:
type: string
description: |
This endpoint allows for efficient bulk creation and updating of subscribers. It mimics our import background jobs and is the recommended method for managing your subscriber base at scale.
Key features:
- Supports both creation and updating of subscribers
- Processes data via import queues for optimal performance
- Changes are typically instant but may take up to 5 minutes in high-load situations
- Ideal for bulk updates, imports, and one-off subscriber modifications
- Does not trigger Flows or automations, ensuring minimal side effects
requestBody:
required: true
content:
application/json:
schema:
type: object
properties:
subscribers:
type: array
description: An array containing between 1 and 1000 subscriber objects.
items:
type: object
properties:
email:
type: string
description: The subscriber's email address. Required for each subscriber.
example: "EMAIL_PLACEHOLDER"
first_name:
type: string
description: The subscriber's first name.
example: "John"
last_name:
type: string
description: The subscriber's last name.
example: "Doe"
tags:
type: string
description: Comma-separated list of tags to add to the subscriber.
example: "newsletter,product_launch"
remove_tags:
type: string
description: Comma-separated list of tags to remove from the subscriber.
example: "old_customer,inactive"
custom_field:
type: string
description: Any additional custom field you want to add or update for the subscriber.
example: "preferred_language"
required:
- email
responses:
"200":
description: Successfully processed subscriber data.
content:
application/json:
schema:
type: object
properties:
result:
type: integer
description: The number of subscribers successfully processed.
example: 1000
/api/v1/batch/emails:
post:
tags:
- emails
security:
- BasicAuth: []
parameters:
- name: site_uuid
in: query
required: true
description: Your site's unique identifier.
schema:
type: string
summary: Create and Send Emails in Bulk
description: |
This endpoint allows you to create and send multiple emails efficiently. It's designed for high-priority email sending with quick processing times.
Key features:
- Supports sending up to 60 emails per request
- Requests are processed in a priority queue
- Most requests are processed within 30 seconds
- Ideal for time-sensitive communications like password resets or important notifications
requestBody:
required: true
content:
application/json:
schema:
type: object
properties:
emails:
type: array
description: An array of 1 to 60 email objects to be sent.
items:
type: object
required:
- to
- from
properties:
to:
type: string
description: The recipient's email address.
example: "EMAIL_PLACEHOLDER"
from:
type: string
description: The sender's email address. Must be an authorized sender in your account.
example: "EMAIL_PLACEHOLDER"
subject:
type: string
description: The subject line of the email.
example: "Your Password Reset Link"
html_body:
type: string
description: The HTML content of the email. Can include placeholders for personalization.
example: "<p>Hello {{name}},</p><p>Click here to reset your password: {{reset_link}}</p>"
transactional:
type: boolean
description: Indicates whether the email is transactional (true) or marketing (false).
example: true
personalizations:
type: object
description: Custom data to be injected into email placeholders.
example:
name: "John Doe"
reset_link: "https://example.com/reset?token=abc123"
responses:
"200":
description: Successfully processed email requests.
content:
application/json:
schema:
type: object
properties:
results:
type: integer
description: The number of email requests successfully processed.
example: 60
/api/v1/batch/events:
post:
tags:
- events
security:
- BasicAuth: []
summary: Create Events in Bulk
description: |
This endpoint allows you to send multiple events to your site. It's a powerful tool for tracking user interactions and behaviors.
Key features:
- Can create new users if they don't exist in your account
- Supports sending up to 1,000 events per request
- Ideal for tracking various user actions like page views, purchases, or custom events
parameters:
- name: site_uuid
in: query
required: true
description: Your site's unique identifier.
schema:
type: string
requestBody:
required: true
content:
application/json:
schema:
type: object
properties:
events:
type: array
description: An array of 1 to 1,000 event objects.
items:
type: object
required:
- type
- email
properties:
type:
type: string
description: The name of the event.
email:
type: string
description: The email of the user associated with the event.
fields:
type: object
description: Additional fields related to the user or event.
details:
type: object
description: Specific details about the event.
date:
type: string
format: date-time
description: The date and time of the event. Use for backfilling historical data.
example:
- type: "$completed_onboarding"
email: "EMAIL_PLACEHOLDER"
- type: "$completed_onboarding"
email: "EMAIL_PLACEHOLDER"
fields:
first_name: "Jane"
last_name: "Doe"
- email: "EMAIL_PLACEHOLDER"
type: "$purchase"
fields:
first_name: "John"
details:
unique:
key: "order_123"
value:
currency: "USD"
amount: 9999
cart:
items:
- product_sku: "PROD-001"
product_name: "Premium Widget"
quantity: 1
abandoned_checkout_url: "https://example.com/cart"
responses:
"200":
description: Successfully processed event data.
content:
application/json:
schema:
type: object
properties:
results:
type: integer
description: The number of events successfully processed.
example: 1000
/api/v1/fetch/broadcasts:
get:
tags:
- broadcasts
security:
- BasicAuth: []
summary: Retrieve Broadcasts
parameters:
- name: site_uuid
in: query
required: true
description: Your site's unique identifier.
schema:
type: string
description: Fetches a list of all broadcasts in your account, providing an overview of your email campaigns.
responses:
"200":
description: Successfully retrieved broadcasts.
content:
application/json:
schema:
type: object
properties:
data:
type: array
items:
$ref: "#/components/schemas/Broadcast"
/api/v1/batch/broadcasts:
post:
tags:
- broadcasts
security:
- BasicAuth: []
summary: Create Multiple Broadcasts
description: |
This endpoint allows you to create multiple email broadcasts efficiently. It's ideal for setting up a series of campaigns or A/B tests.
Key features:
- Supports creating up to 100 broadcasts per request
- Allows for detailed customization of each broadcast
- Useful for scheduling a series of emails or creating variations for testing
parameters:
- name: site_uuid
in: query
required: true
description: Your site's unique identifier.
schema:
type: string
requestBody:
required: true
content:
application/json:
schema:
type: object
properties:
broadcasts:
type: array
description: An array of 1 to 100 broadcast objects.
items:
type: object
properties:
name:
type: string
description: The name of the broadcast campaign.
example: "Summer Sale Announcement"
subject:
type: string
description: The subject line of the email.
example: "Don't Miss Our Biggest Sale of the Year!"
content:
type: string
description: The HTML content of the email. Can include placeholders for personalization.
example: "<p>Hello {{ visitor.first_name }},</p><p>Our summer sale starts tomorrow!</p>"
type:
type: string
description: The type of email template to use. Use "plain" for basic CSS or "raw" for custom HTML.
enum: ["plain", "raw"]
example: "plain"
from:
type: object
description: The sender's information.
properties:
email:
type: string
description: The sender's email address. Must be an authorized sender in your account.
example: "EMAIL_PLACEHOLDER"
name:
type: string
description: The sender's display name.
example: "Your Company Marketing Team"
inclusive_tags:
type: string
description: Comma-separated list of tags. Subscribers must have at least one of these tags to receive the email.
example: "active_customer,high_value"
exclusive_tags:
type: string
description: Comma-separated list of tags. Subscribers with any of these tags will be excluded.
example: "unsubscribed,inactive"
segment_id:
type: string
description: The ID of a pre-defined segment to target with this broadcast.
example: "seg_12345abcde"
batch_size_per_hour:
type: integer
description: The maximum number of emails to send per hour. Use for throttling large campaigns.
example: 1000
responses:
"200":
description: Successfully processed broadcast creation requests.
content:
application/json:
schema:
type: object
properties:
results:
type: integer
description: The number of broadcasts successfully created.
example: 5
/api/v1/fetch/fields:
get:
tags:
- fields
security:
- BasicAuth: []
summary: Retrieve Custom Fields
parameters:
- name: site_uuid
in: query
required: true
description: Your site's unique identifier.
schema:
type: string
description: Fetches a list of all custom fields defined in your account. These fields can be used for subscriber data and segmentation.
responses:
"200":
description: Successfully retrieved custom fields.
content:
application/json:
schema:
type: object
properties:
data:
type: array
items:
$ref: "#/components/schemas/Field"
post:
tags:
- fields
security:
- BasicAuth: []
summary: Create Custom Field
parameters:
- name: site_uuid
in: query
required: true
description: Your site's unique identifier.
schema:
type: string
description: Creates a new custom field in your account. Custom fields allow you to store additional data about your subscribers.
requestBody:
content:
application/json:
schema:
type: object
properties:
field:
type: object
properties:
key:
type: string
description: The unique identifier for the custom field.
example: "loyalty_points"
responses:
"201":
description: Custom field successfully created.
content:
application/json:
schema:
$ref: "#/components/schemas/Field"
/api/v1/fetch/search:
get:
security:
- BasicAuth: []
tags:
- subscribers
summary: Search Subscribers
parameters:
- name: site_uuid
in: query
required: true
description: Your site's unique identifier.
schema:
type: string
description: |
This endpoint allows for advanced searching of your subscriber base. It's designed for Bento Enterprise customers and requires special access.
Key features:
- Returns up to 100 subscribers per page
- Supports various search criteria including creation date, update date, and custom fields
- Ideal for complex segmentation and data analysis tasks
Note: This is an Enterprise-only feature. Please contact Bento support for access and further details.
requestBody:
required: false
content:
application/json:
schema:
type: object
properties:
page:
type: integer
description: The page number of the search results to retrieve.
example: 1
created_at:
type: object
description: Filter by subscriber creation date.
properties:
gt:
type: string
format: date-time
description: Return subscribers created after this date.
lt:
type: string
format: date-time
description: Return subscribers created before this date.
updated_at:
type: object
description: Filter by subscriber last update date.
properties:
gt:
type: string
format: date-time
description: Return subscribers updated after this date.
lt:
type: string
format: date-time
description: Return subscribers updated before this date.
last_event_at:
type: object
description: Filter by the date of the subscriber's last recorded event.
properties:
gt:
type: string
format: date-time
description: Return subscribers with events after this date.
lt:
type: string
format: date-time
description: Return subscribers with events before this date.
unsubscribed_at:
type: object
description: Filter by unsubscribe date.
properties:
gt:
type: string
format: date-time
description: Return subscribers who unsubscribed after this date.
lt:
type: string
format: date-time
description: Return subscribers who unsubscribed before this date.
responses:
"200":
description: Successfully retrieved subscriber search results.
content:
application/json:
schema:
$ref: "#/components/schemas/SearchResult"
/api/v1/fetch/subscribers:
get:
tags:
- subscribers
security:
- BasicAuth: []
summary: Retrieve Subscriber Information
description: Fetch detailed information about one or multiple subscribers in your account.
parameters:
- name: site_uuid
in: query
required: true
description: Your site's unique identifier.
schema:
type: string
- name: email
in: query
description: The email address of the subscriber to retrieve.
schema:
type: string
- name: uuid
in: query
description: The unique identifier of the subscriber. Use this for precise lookups.
schema:
type: string
responses:
"200":
description: Successfully retrieved subscriber information.
content:
application/json:
schema:
$ref: "#/components/schemas/Subscriber"
post:
tags:
- subscribers
summary: Create New Subscriber
description: Creates a new subscriber in your account and queues them for indexing.
parameters:
- name: site_uuid
in: query
required: true
description: Your site's unique identifier.
schema:
type: string
security:
- BasicAuth: []
requestBody:
content:
application/json:
schema:
type: object
properties:
subscriber:
type: object
properties:
email:
type: string
description: The email address of the new subscriber.
example: "EMAIL_PLACEHOLDER"
responses:
"201":
description: Subscriber successfully created.
content:
application/json:
schema:
$ref: "#/components/schemas/Subscriber"
/api/v1/fetch/tags:
get:
tags:
- tags
security:
- BasicAuth: []
summary: Retrieve Tags
description: Fetches a list of all tags in your account. Tags are useful for segmenting your subscriber base.
parameters:
- name: site_uuid
in: query
required: true
description: Your site's unique identifier.
schema:
type: string
responses:
"200":
description: Successfully retrieved tags.
content:
application/json:
schema:
type: object
properties:
data:
type: array
items:
$ref: "#/components/schemas/Tag"
post:
tags:
- tags
security:
- BasicAuth: []
summary: Create New Tag
description: Creates a new tag in your account for subscriber segmentation.
parameters:
- name: site_uuid
in: query
required: true
description: Your site's unique identifier.
schema:
type: string
requestBody:
content:
application/json:
schema:
type: object
properties:
tag:
type: object
properties:
name:
type: string
description: The name of the new tag.
example: "vip_customer"
responses:
"201":
description: Tag successfully created.
content:
application/json:
schema:
$ref: "#/components/schemas/Tag"
/api/v1/fetch/commands:
post:
tags:
- subscribers
security:
- BasicAuth: []
summary: Execute Subscriber Commands
parameters:
- name: site_uuid
in: query
required: true
description: Your site's unique identifier.
schema:
type: string
description: |
This endpoint allows you to execute various commands to modify subscriber data. It's a powerful tool for managing your subscriber base programmatically.
Available commands:
- add_tag: Add a tag to a subscriber
- add_tag_via_event: Add a tag to a subscriber and record it as an event
- remove_tag: Remove a tag from a subscriber
- add_field: Add or update a custom field for a subscriber
- remove_field: Remove a custom field from a subscriber
- subscribe: Mark a subscriber as subscribed
- unsubscribe: Mark a subscriber as unsubscribed
- change_email: Change a subscriber's email address
requestBody:
content:
application/json:
schema:
type: object
properties:
command:
type: array
items:
type: object
properties:
command:
type: string
description: The command to execute.
enum:
[
add_tag,
add_tag_via_event,
remove_tag,
add_field,
remove_field,
subscribe,
unsubscribe,
change_email,
]
email:
type: string
description: The email address of the subscriber to modify.
query:
oneOf:
- type: string
- type: object
description: The data for the command. Format depends on the command type.
example:
- command: add_tag
email: "EMAIL_PLACEHOLDER"
query: "new_customer"
- command: add_tag_via_event
email: "EMAIL_PLACEHOLDER"
query: "product_viewed"
- command: remove_tag
email: "EMAIL_PLACEHOLDER"
query: "inactive"
- command: add_field
email: "EMAIL_PLACEHOLDER"
query:
key: "last_purchase_date"
value: "2023-06-15"
- command: remove_field
email: "EMAIL_PLACEHOLDER"
query: "old_field"
- command: subscribe
email: "EMAIL_PLACEHOLDER"
- command: unsubscribe
email: "EMAIL_PLACEHOLDER"
- command: change_email
email: "EMAIL_PLACEHOLDER"
query: "EMAIL_PLACEHOLDER"
responses:
"200":
description: Commands executed successfully.
content:
application/json:
schema:
$ref: "#/components/schemas/Command"
/api/v1/stats/site:
get:
tags:
- stats
security:
- BasicAuth: []
summary: Retrieve Site Statistics
description: |
Fetches overall statistics for your site. This includes counts of users, subscribers, and unsubscribers.
IMPORTANT: This endpoint should never be used in client-side code to ensure the privacy and security of your account data.
parameters:
- name: site_uuid
in: query
required: true
description: Your site's unique identifier.
schema:
type: string
responses:
"200":
description: Successfully retrieved site statistics.
content:
application/json:
schema:
type: object
properties:
user_count:
type: integer
description: Total number of users in your account.
example: 10000
subscriber_count:
type: integer
description: Number of active subscribers.
example: 8500
unsubscriber_count:
type: integer
description: Number of users who have unsubscribed.
example: 1500
/api/v1/stats/segment:
get:
tags:
- stats
security:
- BasicAuth: []
summary: Retrieve Segment Statistics
description: |
Fetches statistics for a specific segment in your account. This includes counts of users, subscribers, and unsubscribers within the segment.
IMPORTANT: This endpoint should never be used in client-side code to ensure the privacy and security of your account data.
parameters:
- name: site_uuid
in: query
required: true
description: Your site's unique identifier.
schema:
type: string
- name: segment_id
in: query
required: true
description: The unique identifier of the segment you want to analyze.
schema:
type: string
responses:
"200":
description: Successfully retrieved segment statistics.
content:
application/json:
schema:
type: object
properties:
user_count:
type: integer
description: Total number of users in the segment.
example: 5000
subscriber_count:
type: integer
description: Number of active subscribers in the segment.
example: 4200
unsubscriber_count:
type: integer
description: Number of users in the segment who have unsubscribed.
example: 800
/api/v1/experimental/blacklist.json:
get:
tags:
- experimental
security:
- BasicAuth: []
summary: Check Domain or IP Blacklist Status
description: |
This experimental endpoint allows you to check if a domain or IP address is present on various blacklists.
You can provide either a domain or an IP address, but not both in the same request.
parameters:
- name: domain
in: query
description: The domain to check (e.g., "example.com"). Do not include the protocol (http:// or https://).
schema:
type: string
- name: ip
in: query
description: The IP address to check.
schema:
type: string
responses:
"200":
description: Successfully retrieved blacklist information.
content:
application/json:
schema:
type: object
properties:
query:
type: string
description: The domain or IP address that was checked.
description:
type: string
description: A brief description of the result.
results:
type: object
properties:
just_registered:
type: boolean
description: Indicates if the domain was recently registered.
spamhaus:
type: boolean
description: Indicates if the domain/IP is listed on Spamhaus.
nordspam:
type: boolean
description: Indicates if the domain/IP is listed on NordSpam.
spfbl:
type: boolean
description: Indicates if the domain/IP is listed on SPFBL.
sorbs:
type: boolean
description: Indicates if the domain/IP is listed on SORBS.
abusix:
type: boolean
description: Indicates if the domain/IP is listed on Abusix.
/api/v1/experimental/validation:
post:
tags:
- experimental
security:
- BasicAuth: []
summary: Validate Email and User Information
description: |
This experimental endpoint provides basic validation for email addresses and associated user information.
It uses various heuristics to determine the likelihood of the provided information being valid.
parameters:
- name: name
in: query
description: The full name of the contact. Note that this validation is biased towards US Census data and may produce false positives.
schema:
type: string
- name: user_agent
in: query
description: The user agent string from the browser or client application.
schema:
type: string
- name: ip
in: query
description: The users IP address. Returns false for all countries outside of Tier 1.
schema:
type: string
- name: email
required: true
in: query
description: Validates the domains MX records.
schema:
type: string
responses:
"200":
description: Cake successfully retrieved.
content:
application/json:
schema:
type: object
properties:
valid:
type: boolean
/api/v1/experimental/content_moderation:
post:
tags:
- experimental
security:
- BasicAuth: []
summary: Moderate Content
description: This endpoint will return an opinionated moderation score based on the content provided. This is optimised for small amounts of text content, where you never want a link/XSS/etc inside it.
parameters:
- name: content
required: true
in: query
description: The content you wish to moderate.
schema:
type: string
responses:
"200":
description: Cake successfully retrieved.
content:
application/json:
schema:
type: object
properties:
valid:
type: boolean
reasons: