API Integration Segmented By Environment.

[Anonymous]

We are in the process of integrating with your API and would like to create leads in different environments, one for development, one for production, etc. We don't want to pollute real leads with bogus leads used in test scenarios. How might we go about doing this?

[Anonymous]

Sounds like you want a sandbox? Reach out to your account manager to get the ball rolling.

[Anonymous]

Hey Morgan, 

We do the same thing and as Don suggested, you can ask Marketo for a sandbox environment for your testing purposes. 

We have a complete staging environment between our app, SFDC, and Marketo. 

One caveat is you can't easily refresh Marketo sandbox from production unlike SFDC. This is a real pain. 

[Anonymous]

As Don and Justin mentioned a sanbox is the best option for this. Another alternative is to create a convention when you create test leads in your Marketo instance, so you know they are test leads. For example, create a custom field called TestLead, and then mark this field trust for Test Leads. This way you can easily delete these leads later. 

[Anonymous]

Hi Morgan
If you don't have sandbox, you can create two workspaces and two lead partitions for production and development.
You can control test users permission also.
Note that:
- Access control is REST only
- You can not delete test attributes from lead database forever, hide only