Internal blueprint and generic endpoints

[kalbfled]

User Story - Business Need

We currently use pipedream.com as a temporary server for modifying requests. This ticket will use our own service as a server to receive test http requests.

• [ ] Ticket is understood, and QA has been contacted (if the ticket has a QA label).

User Story(ies)

As a Notify developer, I want the API to include internal endpoints So that we can integrate with Vetext, etc.

Additional Info and Resources

This ticket is being created along with infra 775 to point Dev to these new internal endpoints for vetext forwarding.

Engineering Checklist

• [ ] Create a new blueprint for the path /internal
• [ ] Use the new blueprint to create two endpoints:
  • [ ] /internal/generic_one
  • [ ] /internal/generic_two
• [ ] The implementation of each route should log the Flask request object and return 200

Acceptance Criteria

• [ ] POST requests to /internal/generic_one and /internal/generic_two log the request with a return value of 200

QA Considerations

• [ ] work with QA for testing and validation

• These routes do not need OpenAPI or Postman collection entries.

[cris-oddball]

@kalbfled this needs to work for both Dev and Perf. Does this ticket need to be updated to account for both environments?