You don't usually use the GET HTTP verb to create or modify records in a RESTful API. 

• GET is Made for Retrieval (Read Operations): The GET verb's basic goal is to ask for and get data from a given source. Intended for read-only activities, it should not affect the state of the server. 
• Creating or updating records naturally means changing the state of the server; for example, this could involve adding a new entry to a database or altering an existing one. Using GET for these activities would go against the intended meaning and semantics of the verb.
• By default, when you make a GET request over plain HTTP (http://...), the entire request, including the URL (which can contain data in the query string), is transmitted in plain text. Anyone intercepting the network traffic can easily read this information. If you were to try and send data for creating or updating via the URL in a GET request, this sensitive information would be exposed in plain text. This could include user credentials, personal details, or any other data you're trying to save or modify.