title: Multiple Dtos for same entity
body: <p>Is it a good practice to use multiple DTO's for same entity in different API endpoints. For example:
  I have a api endpoint which accpets the following Dto:</p>
  
  <pre><code>public class AddressDto
  {
      public string City { get; set; }
      public string Country { get; set; }
      public string Contact { get; set; }
      public string Street1 { get; set; }
      public string Street2 { get; set; }
      public string State { get; set; }
      public string Zip { get; set; }
  }
  </code></pre>
  
  <p>And now there is second Api which accepts the same dto but in that api call I'm using only <code>Streer1, Street2, Contact</code> all other are ignored.</p>
  
  <p>Should I make another <code>DTO</code> for second <code>api endpoint</code> like:</p>
  
  <pre><code>public class AddressDtoForSecondAPI
  {
      public string Contact { get; set; }
      public string Street1 { get; set; }
      public string Street2 { get; set; }
  }
  </code></pre>