Skip to content

feat(emails): add POST /emails/schedule for programmatic campaign creation - #310

Open
brayanjeshua wants to merge 1 commit into
GoHighLevel:mainfrom
brayanjeshua:feat/email-schedule-create-endpoint
Open

feat(emails): add POST /emails/schedule for programmatic campaign creation#310
brayanjeshua wants to merge 1 commit into
GoHighLevel:mainfrom
brayanjeshua:feat/email-schedule-create-endpoint

feat(emails): add POST /emails/schedule endpoint for campaign creation

7ec3cba
Select commit
Loading
Failed to load commit list.
Orca Security (US) / Orca Security - Infrastructure as Code succeeded Jul 11, 2026 in 19s

Orca Security Scan Summary

Status Check Issues by priority
Passed Passed Infrastructure as Code high 0   medium 0   low 6   info 22 View in Orca
🛡️ The following IaC misconfigurations have been detected
NAME FILE
low Response on operations that should have a body has undefined schema apps/emails.json View in code
low Response on operations that should have a body has undefined schema apps/emails.json View in code
low Response on operations that should have a body has undefined schema apps/emails.json View in code
low Response on operations that should have a body has undefined schema apps/emails.json View in code
low Response on operations that should have a body has undefined schema apps/emails.json View in code
low Response Code Missing (v3) apps/emails.json View in code
info Object Without Required Property apps/emails.json View in code
info Object Without Required Property apps/emails.json View in code
info Object Without Required Property apps/emails.json View in code
info Object Without Required Property apps/emails.json View in code
info Object Without Required Property apps/emails.json View in code
info Object Without Required Property apps/emails.json View in code
info Object Without Required Property apps/emails.json View in code
info Default Invalid apps/emails.json View in code
info Template Path With No Corresponding Path Parameter apps/emails.json View in code
info Template Path With No Corresponding Path Parameter apps/emails.json View in code
info Template Path With No Corresponding Path Parameter apps/emails.json View in code
info Components Object Fixed Field Key Improperly Named apps/emails.json View in code
info Components Object Fixed Field Key Improperly Named apps/emails.json View in code
info Components Object Fixed Field Key Improperly Named apps/emails.json View in code
info Security Requirement Object With Wrong Scopes apps/emails.json View in code
info Security Requirement Object With Wrong Scopes apps/emails.json View in code
info Security Requirement Object With Wrong Scopes apps/emails.json View in code
info Security Requirement Object With Wrong Scopes apps/emails.json View in code
info Security Requirement Object With Wrong Scopes apps/emails.json View in code
... ... ... ...

Annotations

Check warning on line 578 in apps/emails.json

See this annotation in the file changed.

@orca-security-us orca-security-us / Orca Security - Infrastructure as Code

[INFO] Object Without Required Property 

Details:
OpenAPI v3 specification objects lack required fields defined by the standard,
causing schema validation failures and potential client integration issues.
Missing required properties prevent proper API documentation parsing and code
generation. Include all mandatory fields as specified in the OpenAPI 3.0
specification.

Recommendation:
tags has all required fields

Check warning on line 1458 in apps/emails.json

See this annotation in the file changed.

@orca-security-us orca-security-us / Orca Security - Infrastructure as Code

[INFO] Object Without Required Property 

Details:
OpenAPI v3 specification objects lack required fields defined by the standard,
causing schema validation failures and potential client integration issues.
Missing required properties prevent proper API documentation parsing and code
generation. Include all mandatory fields as specified in the OpenAPI 3.0
specification.

Recommendation:
tags has all required fields

Check warning on line 315 in apps/emails.json

See this annotation in the file changed.

@orca-security-us orca-security-us / Orca Security - Infrastructure as Code

[INFO] Object Without Required Property 

Details:
OpenAPI v3 specification objects lack required fields defined by the standard,
causing schema validation failures and potential client integration issues.
Missing required properties prevent proper API documentation parsing and code
generation. Include all mandatory fields as specified in the OpenAPI 3.0
specification.

Recommendation:
tags has all required fields

Check warning on line 756 in apps/emails.json

See this annotation in the file changed.

@orca-security-us orca-security-us / Orca Security - Infrastructure as Code

[INFO] Object Without Required Property 

Details:
OpenAPI v3 specification objects lack required fields defined by the standard,
causing schema validation failures and potential client integration issues.
Missing required properties prevent proper API documentation parsing and code
generation. Include all mandatory fields as specified in the OpenAPI 3.0
specification.

Recommendation:
tags has all required fields

Check warning on line 231 in apps/emails.json

See this annotation in the file changed.

@orca-security-us orca-security-us / Orca Security - Infrastructure as Code

[INFO] Object Without Required Property 

Details:
OpenAPI v3 specification objects lack required fields defined by the standard,
causing schema validation failures and potential client integration issues.
Missing required properties prevent proper API documentation parsing and code
generation. Include all mandatory fields as specified in the OpenAPI 3.0
specification.

Recommendation:
tags has all required fields

Check warning on line 670 in apps/emails.json

See this annotation in the file changed.

@orca-security-us orca-security-us / Orca Security - Infrastructure as Code

[INFO] Object Without Required Property 

Details:
OpenAPI v3 specification objects lack required fields defined by the standard,
causing schema validation failures and potential client integration issues.
Missing required properties prevent proper API documentation parsing and code
generation. Include all mandatory fields as specified in the OpenAPI 3.0
specification.

Recommendation:
tags has all required fields

Check warning on line 401 in apps/emails.json

See this annotation in the file changed.

@orca-security-us orca-security-us / Orca Security - Infrastructure as Code

[INFO] Object Without Required Property 

Details:
OpenAPI v3 specification objects lack required fields defined by the standard,
causing schema validation failures and potential client integration issues.
Missing required properties prevent proper API documentation parsing and code
generation. Include all mandatory fields as specified in the OpenAPI 3.0
specification.

Recommendation:
tags has all required fields

Check warning on line 424 in apps/emails.json

See this annotation in the file changed.

@orca-security-us orca-security-us / Orca Security - Infrastructure as Code

[INFO] Default Invalid 

Details:
Schema objects with 'default' values that don't match their defined type create
validation inconsistencies and may cause unexpected API behavior. Ensure default
values align with the schema's declared type.

Recommendation:
The field 'default' should be consistent with the type

Check warning on line 608 in apps/emails.json

See this annotation in the file changed.

@orca-security-us orca-security-us / Orca Security - Infrastructure as Code

[INFO] Template Path With No Corresponding Path Parameter 

Details:
OpenAPI path templates containing parameters (e.g., `/users/{userId}`) must
define corresponding path parameters in operation objects with 'in' set to
'path'. Missing parameter definitions break API contracts and cause runtime
errors when consumers attempt invalid requests. Define all templated path
parameters in operation parameter lists.

Recommendation:
Template path parameter should have an operation parameter with the same name and
'in' set to 'path'

Check warning on line 590 in apps/emails.json

See this annotation in the file changed.

@orca-security-us orca-security-us / Orca Security - Infrastructure as Code

[INFO] Template Path With No Corresponding Path Parameter 

Details:
OpenAPI path templates containing parameters (e.g., `/users/{userId}`) must
define corresponding path parameters in operation objects with 'in' set to
'path'. Missing parameter definitions break API contracts and cause runtime
errors when consumers attempt invalid requests. Define all templated path
parameters in operation parameter lists.

Recommendation:
Template path parameter should have an operation parameter with the same name and
'in' set to 'path'

Check warning on line 599 in apps/emails.json

See this annotation in the file changed.

@orca-security-us orca-security-us / Orca Security - Infrastructure as Code

[INFO] Template Path With No Corresponding Path Parameter 

Details:
OpenAPI path templates containing parameters (e.g., `/users/{userId}`) must
define corresponding path parameters in operation objects with 'in' set to
'path'. Missing parameter definitions break API contracts and cause runtime
errors when consumers attempt invalid requests. Define all templated path
parameters in operation parameter lists.

Recommendation:
Template path parameter should have an operation parameter with the same name and
'in' set to 'path'

Check warning on line 817 in apps/emails.json

See this annotation in the file changed.

@orca-security-us orca-security-us / Orca Security - Infrastructure as Code

[INFO] Components Object Fixed Field Key Improperly Named 

Details:
Component object field keys in OpenAPI specifications must follow naming
conventions allowing only alphanumeric characters, periods, hyphens, and
underscores. Non-compliant keys cause parsing errors and break tooling
compatibility. Use keys matching the pattern `^[a-zA-Z0-9\.\-_]+$`.

Recommendation:
components.{{securitySchemes}}.{{Location-Access-Only}} is properly named

Check warning on line 801 in apps/emails.json

See this annotation in the file changed.

@orca-security-us orca-security-us / Orca Security - Infrastructure as Code

[INFO] Components Object Fixed Field Key Improperly Named 

Details:
Component object field keys in OpenAPI specifications must follow naming
conventions allowing only alphanumeric characters, periods, hyphens, and
underscores. Non-compliant keys cause parsing errors and break tooling
compatibility. Use keys matching the pattern `^[a-zA-Z0-9\.\-_]+$`.

Recommendation:
components.{{securitySchemes}}.{{Location-Access}} is properly named

Check warning on line 809 in apps/emails.json

See this annotation in the file changed.

@orca-security-us orca-security-us / Orca Security - Infrastructure as Code

[INFO] Components Object Fixed Field Key Improperly Named 

Details:
Component object field keys in OpenAPI specifications must follow naming
conventions allowing only alphanumeric characters, periods, hyphens, and
underscores. Non-compliant keys cause parsing errors and break tooling
compatibility. Use keys matching the pattern `^[a-zA-Z0-9\.\-_]+$`.

Recommendation:
components.{{securitySchemes}}.{{Agency-Access}} is properly named

Check warning on line 310 in apps/emails.json

See this annotation in the file changed.

@orca-security-us orca-security-us / Orca Security - Infrastructure as Code

[INFO] Security Requirement Object With Wrong Scopes 

Details:
OpenAPI security requirements define scopes for authentication schemes, but only
OAuth2 and OpenID Connect support scope-based authorization. Specifying scopes
for API Key or HTTP authentication types creates invalid configurations that fail
validation. Remove scopes from security requirements using authentication types
that do not support them.

Recommendation:
'security.Location-Access' has no scopes defined for security scheme of type
'http'

Check warning on line 573 in apps/emails.json

See this annotation in the file changed.

@orca-security-us orca-security-us / Orca Security - Infrastructure as Code

[INFO] Security Requirement Object With Wrong Scopes 

Details:
OpenAPI security requirements define scopes for authentication schemes, but only
OAuth2 and OpenID Connect support scope-based authorization. Specifying scopes
for API Key or HTTP authentication types creates invalid configurations that fail
validation. Remove scopes from security requirements using authentication types
that do not support them.

Recommendation:
'security.Location-Access' has no scopes defined for security scheme of type
'http'

Check warning on line 751 in apps/emails.json

See this annotation in the file changed.

@orca-security-us orca-security-us / Orca Security - Infrastructure as Code

[INFO] Security Requirement Object With Wrong Scopes 

Details:
OpenAPI security requirements define scopes for authentication schemes, but only
OAuth2 and OpenID Connect support scope-based authorization. Specifying scopes
for API Key or HTTP authentication types creates invalid configurations that fail
validation. Remove scopes from security requirements using authentication types
that do not support them.

Recommendation:
'security.Location-Access' has no scopes defined for security scheme of type
'http'

Check warning on line 396 in apps/emails.json

See this annotation in the file changed.

@orca-security-us orca-security-us / Orca Security - Infrastructure as Code

[INFO] Security Requirement Object With Wrong Scopes 

Details:
OpenAPI security requirements define scopes for authentication schemes, but only
OAuth2 and OpenID Connect support scope-based authorization. Specifying scopes
for API Key or HTTP authentication types creates invalid configurations that fail
validation. Remove scopes from security requirements using authentication types
that do not support them.

Recommendation:
'security.Location-Access' has no scopes defined for security scheme of type
'http'

Check warning on line 226 in apps/emails.json

See this annotation in the file changed.

@orca-security-us orca-security-us / Orca Security - Infrastructure as Code

[INFO] Security Requirement Object With Wrong Scopes 

Details:
OpenAPI security requirements define scopes for authentication schemes, but only
OAuth2 and OpenID Connect support scope-based authorization. Specifying scopes
for API Key or HTTP authentication types creates invalid configurations that fail
validation. Remove scopes from security requirements using authentication types
that do not support them.

Recommendation:
'security.Location-Access' has no scopes defined for security scheme of type
'http'

Check warning on line 46 in apps/emails.json

See this annotation in the file changed.

@orca-security-us orca-security-us / Orca Security - Infrastructure as Code

[INFO] Unknown Property 

Details:
OpenAPI v3.0 specifications contain properties not recognized by the standard
schema, indicating potential typos, deprecated fields, or custom extensions.
Unknown properties may cause validation failures or unexpected API behavior.
Review and remove unrecognized fields or properly namespace custom extensions
using 'x-' prefix.

Recommendation:
The field 'default' is known in the parameters object
View more details on Orca Security (US)